| /linux-4.4.14/Documentation/scsi/ |
| D | megaraid.txt | 8 user applications in a similar way. They understand the same firmware control
9 commands. Furthermore, the applications also can treat different classes of
11 interfaces with the applications on one side and all the low level drivers
56 The applications interface with the common module via the character device
61 applications into uioc_t. After driver handles the uioc_t, the common module
62 will convert that back into the old format before returning to applications.
64 As new applications evolve and replace the old ones, the old packet format
|
| D | scsi-generic.txt | 67 Another approach is to look at the applications that use the sg driver.
|
| D | hpsa.txt | 102 For compatibility with applications written for the cciss driver, many, but
|
| D | libsas.txt | 339 I expect user space applications to actually create a
367 to which user space applications can send SMP requests and
|
| D | ChangeLog.megaraid | 466 vi. Add support for 64-bit applications. Current drivers assume only
467 32-bit applications, even on 64-bit platforms. Use the "data" and
560 i. Independent module to interact with userland applications and
|
| /linux-4.4.14/Documentation/fb/ |
| D | api.txt | 10 This document describes the frame buffer API used by applications to interact
16 the recommended API implementation, but applications should be prepared to
147 Screen information are queried by applications using the FBIOGET_FSCREENINFO
153 be directly modified by applications, but can be changed by the driver when an
221 To modify variable information, applications call the FBIOPUT_VSCREENINFO
226 applications should call the FBIOGET_VSCREENINFO ioctl and modify only the
239 for applications when using RGB and grayscale formats, as well as legacy
242 To select a format, applications set the fb_var_screeninfo bits_per_pixel field
246 - For grayscale formats, applications set the grayscale field to one. The red,
247 blue, green and transp fields must be set to 0 by applications and ignored by
[all …]
|
| D | udlfb.txt | 20 non-gaming and non-video applications.
37 * X servers and other applications can use the standard fbdev interface
66 At that point, a /dev/fb? interface will be present for user-mode applications
105 Standard fbdev applications that use mmap but that do not
|
| D | 00-INDEX | 9 - The frame buffer API between applications and buffer devices.
|
| D | deferred_io.txt | 42 How to use it: (for applications)
|
| D | intelfb.txt | 44 used by standard graphics applications (XFree86). Depending on your
|
| D | intel810.txt | 119 used by standard graphics applications (XFree86). The default
|
| /linux-4.4.14/arch/arm/mach-sti/ |
| D | Kconfig | 34 and other digital audio/video applications using Flattned Device
44 and other digital audio/video applications using Flattened Device
54 and other digital audio/video applications using Flattened Device
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/ |
| D | brcm,nsp.txt | 5 and management applications as well as residential router/gateway
6 applications. The SoC features dual core Cortex A9 ARM CPUs, integrating
|
| /linux-4.4.14/Documentation/ |
| D | SAK.txt | 7 masquerading as login applications. Users need to be taught to enter
43 2: On the PC keyboard, SAK kills all applications which have
47 actually want killed. This is because these applications are
87 applications to malfunction - test everything well.
|
| D | unshare.txt | 38 call, applications can selectively choose which resources to share
46 usefulness of Linux threads for applications that would like to control
57 even non-threaded applications if they have a need to disassociate
112 new context flags without requiring a rebuild of old applications.
294 applications using unshare.
|
| D | sysfs-rules.txt | 10 low-level userspace applications, with a new kernel release, the users
42 applications that look for devices in sysfs.
61 - applications need to handle spaces and characters like '!' in
182 Userspace applications can, however, expect the format and contents of
|
| D | java.txt | 7 You can execute Java applications and Java Applets just like any
17 variable to use Java applications that make use of any
31 support for Java applications:
|
| D | pi-futex.txt | 23 user-space applications. In the best-case, it can help achieve
66 [this is a quite common scenario for most non-trivial RT applications],
|
| D | ldm.txt | 28 To prevent legacy applications from repartitioning the disk, the LDM creates a
|
| D | rtc.txt | 95 exclusive access to the device for your applications.
102 probably a lot more useful to people interested in writing applications
|
| D | dell_rbu.txt | 7 It does not cover the support needed from applications to enable the BIOS to
|
| D | ntb.txt | 38 besides Netdev, however no other applications have yet been written.
|
| D | binfmt_misc.txt | 95 - enable support for packed DOS applications (pre-configured dosemu hdimages):
|
| /linux-4.4.14/Documentation/networking/ |
| D | tcp-thin.txt | 16 applications, we have seen that they often produce thin streams
35 Since these mechanisms are targeted at time-dependent applications,
45 "Improving latency for interactive, thin-stream applications over
|
| D | udplite.txt | 30 Several applications have been ported successfully to UDP-Lite. Ethereal
32 Porting applications to UDP-Lite is straightforward: only socket level and
66 checksummed. This is useful for RTP applications which have a 12-byte
|
| D | dccp.txt | 27 given applications, see section 10 of RFC 4340.
89 preferable over the latter two, since often applications will use the same
|
| D | can.txt | 85 have to be implemented in user space applications. Also, most
94 to user space applications and which builds upon the Linux network
158 provide a socket interface to user space applications which builds
169 The network transparent access of multiple applications leads to the
170 problem that different applications may be interested in the same
187 applications may run on the same or different nodes without any
213 networking behaviour for CAN applications. Due to some requests from
596 Implementation hint for new CAN applications:
599 data structure for CAN_RAW based applications. When the application is
1174 canfd_frame.len for userspace applications and inside the Linux network
|
| D | ieee802154.txt | 122 expected in applications such as wireless Sensor Networks. [RFC4944] defines
|
| D | cdc_mbim.txt | 46 Such userspace applications includes, but are not limited to:
228 service. Userspace applications supporting specific MBIM DSS services
|
| D | cxgb.txt | 308 Binding netserver and netperf (or other applications) to particular
317 If you are just running user-space applications such as ftp, telnet,
|
| D | rds.txt | 16 applications to use a single socket to talk to any other process in the
136 This isn't a trivial problem, but applications can deal with
|
| D | openvswitch.txt | 36 applications to work with any version of the flow key, past or future.
151 compatibility for applications that follow the rules listed under
|
| D | xfrm_sync.txt | 106 in order to not change existing applications such as racoon
|
| D | ipvs-sysctl.txt | 82 9 - binding destination, template checks and applications
|
| /linux-4.4.14/drivers/staging/most/Documentation/ |
| D | driver_usage.txt | 4 The Media Oriented Systems Transport (MOST) driver gives Linux applications
24 automotive applications.
88 Standard networking applications (e.g. iperf) can by used to access
92 Standard video applications (e.g. VLC) can by used to access the
96 Standard sound applications (e.g. aplay, arecord, audacity) can by
153 make it accessible to user space applications, the attribute file 'add_link' is
|
| /linux-4.4.14/drivers/media/usb/pvrusb2/ |
| D | Kconfig | 27 This is not generally needed for v4l applications,
28 although certain applications are optimized to take
|
| /linux-4.4.14/Documentation/vm/ |
| D | hwpoison.txt | 41 of applications. KVM support requires a recent qemu-kvm release.
45 address. This in theory allows other applications to handle
46 memory failures too. The expection is that near all applications
61 This allows applications who can process memory errors in a gentle
67 This is best for memory error unaware applications and default
|
| D | overcommit-accounting | 11 applications. Classic example is code using sparse arrays
23 Useful for applications that want to guarantee their
|
| D | transhuge.txt | 5 Performance critical computing applications dealing with large memory
15 The reason applications are running faster is because of two
70 hugepages. It requires no modifications for applications to take
77 lived page allocations even for hugepage unaware applications that
201 identify what applications are using transparent huge pages, it is
298 == Optimizing the applications ==
|
| D | hugetlbpage.txt | 117 requested by applications. Writing any non-zero value into this file
265 If the user applications are going to request huge pages using mmap system
306 applications are going to use only shmat/shmget system calls or mmap with
313 applications to use any combination of mmaps and shm* calls, though the mount of
|
| D | split_page_table_lock | 6 multi-threaded applications due high contention on the lock. To improve
|
| D | numa_memory_policy.txt | 88 inheritable across exec(). Thus, only NUMA-aware applications may
281 Thanks to the consistent remapping, applications preparing
361 it down. However, this might not be appropriate for all applications.
370 for user space applications reside in a package that is not part of
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | uvcvideo.txt | 23 The first one allows generic V4L2 applications to use XU controls by mapping
36 The UVC driver provides an API for user space applications to define so-called
55 For applications that need to access XU controls directly, e.g. for testing
60 A call to this ioctl allows applications to send queries to the UVC driver that
109 applications can access vendor-defined UVC control through the V4L2
112 To create a mapping, applications fill the uvc_xu_control_mapping
|
| D | README.ir | 34 applications to access the remote via /dev/input/event<n> devices.
|
| D | README.ivtv | 15 NOTE: 'normal' TV applications do not work with this driver, you need
38 * Provides a framebuffer (allowing X applications to appear on the video
|
| D | zr364xx.txt | 27 You can then use the camera with V4L2 compatible applications, for example Ekiga.
|
| D | meye.txt | 7 This driver enable the use of video4linux compatible applications with the
|
| D | fimc.txt | 80 detects such cases but the applications should prevent them to avoid an
|
| D | soc-camera.txt | 32 multiple cameras per interface, although most applications have only one camera
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | powersave.txt | 9 appropriately when no operation is required. When no applications use
20 (the minimum value) isn't recommended because many applications try to
|
| D | timestamping.txt | 19 timestamps allow for applications to keep track of the 'fullness' of
112 audio applications...
118 impacting legacy applications, a new STATUS_EXT ioctl is introduced
135 information. To make sure applications are not confused, a
|
| D | Jack-Controls.txt | 5 to user space. This means userspace applications like pulseaudio can
|
| D | Channel-Mapping-API.txt | 19 explicitly, and applications had no way to know which channel
20 corresponds to which (speaker) position. Thus, applications applied
|
| D | OSS-Emulation.txt | 116 This will lead to some problems for some applications like quake or
150 conversion and useful for MMAP-applications.
|
| /linux-4.4.14/drivers/media/pci/ivtv/ |
| D | Kconfig | 37 applications to obtain PCM audio data from Conexant cx23415/cx23416
40 The ALSA interface has much wider use in user applications performing
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | sysfs-tagging.txt | 11 To avoid that problem and allow existing applications in network
17 in the directories and applications only see a limited set of
|
| D | 9p.txt | 15 The best detailed explanation of the Linux implementation and applications of
19 Other applications are described in the following papers:
38 For Plan 9 From User Space applications (http://swtch.com/plan9)
159 For information on Plan 9 from User Space (Plan 9 applications and libraries
|
| D | relay.txt | 4 The relay interface provides a means for kernel applications to
13 buffer. User space applications mmap() or read() from the relay files
133 poll() POLLIN/POLLRDNORM/POLLERR supported. User applications are
147 mounted when user space applications need access to the buffer
262 double-buffering to N buffers, and they also allow applications to
264 be important for some high-volume applications. The number and size
275 default per-cpu set. This can be useful for applications interested
432 can be written to later. This would typically be used in applications
435 may not happen immediately after the slot is reserved, applications
458 Some applications may want to keep a channel around and re-use it
|
| D | sysfs-pci.txt | 75 ROM file, if available. It's disabled by default, however, so applications
102 The legacy_io file is a read/write file that can be used by applications to
|
| D | xfs.txt | 107 systems and applications, since 64 bits inode numbers might
108 cause problems for some applications that cannot handle
109 large inode numbers. If applications are in use which do
118 user applications to avoid inefficient read/modify/write
|
| D | dnotify.txt | 6 The intention of directory notification is to allow user applications
|
| D | inotify.txt | 44 ordering is crucial to existing applications such as Beagle. Imagine
|
| D | fiemap.txt | 140 is mounted. In other words, user applications may only read the
143 clear; user applications must not try reading or writing to the
|
| /linux-4.4.14/fs/notify/dnotify/ |
| D | Kconfig | 8 superior alternatives, but some applications may still rely on
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.mISDN | 3 It was designed to allow a broad range of applications and interfaces
|
| D | INTERFACE.CAPI | 11 Kernel CAPI operates as a dispatching layer between CAPI applications and CAPI
14 to CAPI applications. CAPI applications also register with Kernel CAPI,
54 Kernel CAPI forwards registration requests from applications (calls to CAPI
67 Deregistration requests (CAPI operation CAPI_RELEASE) from applications are
123 releasing all registered applications
132 applications with the device
|
| D | README.avmb1 | 82 -r--r--r-- 1 root root 0 Jul 1 14:03 applications
92 /proc/capi/applications:
|
| D | README.gigaset | 159 kernel and user space applications. For user space access, the module
162 Legacy ISDN4Linux applications are supported via the capidrv
180 applications only. Most distributions provide some configuration utility
283 This holds for both CAPI 2.0 and ISDN4Linux applications. Unimodem mode
|
| D | README.x25 | 169 There are currently no real X.25 applications available. However, for
|
| D | README.hysdn | 56 compliant devices with either CAPI 2.0 applications
|
| /linux-4.4.14/kernel/ |
| D | Kconfig.preempt | 31 applications to run more 'smoothly' even when the system is
47 This allows applications to run more 'smoothly' even when the
|
| /linux-4.4.14/net/bluetooth/rfcomm/ |
| D | Kconfig | 7 applications.
|
| /linux-4.4.14/fs/dlm/ |
| D | Kconfig | 8 applications.
|
| /linux-4.4.14/net/irda/ircomm/ |
| D | Kconfig | 9 use all existing applications that understands TTY's with an
|
| /linux-4.4.14/drivers/staging/gdm724x/ |
| D | Kconfig | 11 used for AT commands and DM monitoring applications.
|
| /linux-4.4.14/drivers/ipack/ |
| D | Kconfig | 14 industrial control applications.
|
| /linux-4.4.14/Documentation/arm/stm32/ |
| D | stm32f429-overview.txt | 6 The STM32F429 is a Cortex-M4 MCU aimed at various applications.
|
| /linux-4.4.14/net/iucv/ |
| D | Kconfig | 15 Select this option if you want to use AF_IUCV socket applications
|
| /linux-4.4.14/net/packet/ |
| D | Kconfig | 8 The Packet protocol is used by applications which communicate
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | overview.txt | 10 sensors used in applications such as fan speed control and temperature
41 applications it it useful to be able to capture data based on some
|
| D | sysfs-bus-iio-ad7192 | 16 In bridge applications, such as strain gauges and load cells,
|
| /linux-4.4.14/net/bluetooth/cmtp/ |
| D | cmtp.h | 93 struct list_head applications; member
|
| D | capi.c | 85 list_add_tail(&app->list, &session->applications); in cmtp_application_add()
105 list_for_each(p, &session->applications) { in cmtp_application_get()
520 list_for_each(p, &session->applications) { in cmtp_proc_show()
|
| D | core.c | 373 INIT_LIST_HEAD(&session->applications); in cmtp_add_connection()
|
| /linux-4.4.14/Documentation/arm/SA1100/ |
| D | LART | 5 applications. It has 32 MB DRAM, 4MB Flash ROM, double RS232 and all
|
| D | serial_UART | 38 must ensure your user space applications make use of the correct device
|
| /linux-4.4.14/drivers/staging/rdma/ipath/ |
| D | Kconfig | 9 as IP-over-InfiniBand as well as with userspace applications
|
| /linux-4.4.14/drivers/hid/usbhid/ |
| D | Kconfig | 59 useful for embedded applications or simple keyboards.
75 useful for embedded applications or simple mice.
|
| /linux-4.4.14/drivers/virt/ |
| D | Kconfig | 21 to drivers and applications related to the Freescale hypervisor:
|
| /linux-4.4.14/drivers/android/ |
| D | Kconfig | 28 applications in a mixed environment.
|
| /linux-4.4.14/net/ipx/ |
| D | Kconfig | 49 bind call. So applications should always initialize the node field
55 disabled. This might break existing applications, especially RIP/SAP
|
| /linux-4.4.14/drivers/media/platform/vivid/ |
| D | Kconfig | 17 It is highly configurable and is ideal for testing applications.
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-frequency-adf4350 | 16 applications, the reference frequency used by the PLL may
|
| D | sysfs-bus-pci | 185 Userspace applications interested in knowing the
197 Userspace applications interested in knowing the
213 Userspace applications interested in knowing the
235 Userspace applications can read this file to determine the
248 Userspace applications can read and write to this file to
|
| D | sysfs-firmware-acpi | 8 by boot splash applications in order to interact with
177 and other user space applications so that the machine won't shutdown
|
| D | sysfs-class-cxl | 27 userspace applications to that many userspace interrupts. Must
|
| /linux-4.4.14/Documentation/mic/ |
| D | scif_overview.txt | 33 SCIF shows the performance advantages of SCIF for HPC applications and runtimes.
68 Here is some pseudo code for an example of how two applications on two PCIe
|
| D | mic_overview.txt | 16 for applications. A key benefit of our solution is that it leverages
|
| /linux-4.4.14/net/tipc/ |
| D | Kconfig | 12 cluster applications for many years.
|
| /linux-4.4.14/Documentation/hid/ |
| D | hidraw.txt | 22 A benefit of hidraw is that its use by userspace applications is independent
31 and udev rule-dependent, applications should use libudev to locate hidraw
115 purpose, and can serve as a starting point for developing applications using
|
| D | hid-sensor.txt | 46 data fields. It is difficult to have a common input event to user space applications,
154 This allows some differentiating use cases, where vendor can provide applications.
|
| /linux-4.4.14/drivers/isdn/mISDN/ |
| D | Kconfig | 18 This module may be used for special applications that require
|
| /linux-4.4.14/drivers/staging/media/ |
| D | Kconfig | 8 so, they won't likely work fine with the existing applications.
|
| /linux-4.4.14/Documentation/locking/ |
| D | rt-mutex.txt | 27 magic bullet for poorly designed applications, but it allows
28 well-designed applications to use userspace locks in critical parts of
|
| /linux-4.4.14/Documentation/dvb/ |
| D | faq.txt | 54 3. Which other DVB applications exist?
76 the TuxBox CVS many interesting DVB applications and the dBox2
142 applications
|
| D | ci.txt | 39 purposes only, they can become full fledged applications if necessary.
102 implemented by most applications. Hence this area is revisited.
|
| /linux-4.4.14/Documentation/devicetree/bindings/misc/ |
| D | fsl,qoriq-mc.txt | 5 network-oriented packet processing applications. After the fsl-mc
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/ |
| D | ti-am437x-vpfe.txt | 5 applications. The capture module provides the system interface and the
|
| /linux-4.4.14/drivers/gpu/drm/imx/ |
| D | Kconfig | 20 and also for applications using the legacy framebuffer API
|
| /linux-4.4.14/Documentation/timers/ |
| D | NO_HZ.txt | 8 applications and for real-time applications.
23 are running realtime applications or certain types of HPC
58 degrade your applications performance. If this describes your workload,
110 for applications with aggressive real-time response constraints because
162 Real-time applications needing to take actions based on CPU time
179 useful for many types of real-time and compute-intensive applications.
|
| D | hrtimers.txt | 58 The primary users of precision timers are user-space applications that
67 The increasing demand for realtime and multimedia applications along
|
| /linux-4.4.14/net/decnet/ |
| D | TODO | 15 o Lots of testing with real applications
|
| /linux-4.4.14/arch/metag/ |
| D | Kconfig.soc | 59 applications.
|
| /linux-4.4.14/fs/xfs/ |
| D | Kconfig | 63 for media streaming applications, but is also useful as a generic
67 to applications via the inherit-realtime directory inode flag.
|
| /linux-4.4.14/arch/arm/mach-bcm/ |
| D | Kconfig | 46 and management applications as well as residential router/gateway
47 applications. The SoC features dual core Cortex A9 ARM CPUs,
|
| /linux-4.4.14/mm/ |
| D | Kconfig | 203 # Heavily threaded applications may benefit from splitting the mm-wide
321 Recommended for use with KVM, or with other duplicative applications.
399 huge tlb transparently to the applications whenever possible.
401 applications by speeding up page faults during memory
418 memory footprint of applications without a guaranteed
419 benefit but it will work automatically for all applications.
425 performance improvement benefit to the applications using
427 memory footprint of applications without a guaranteed
|
| /linux-4.4.14/Documentation/arm64/ |
| D | tagged-pointers.txt | 22 This means that signal handlers in applications making use
|
| /linux-4.4.14/arch/parisc/ |
| D | Kconfig | 217 compatibility with 32bit applications, a page size of 4KB should be
332 This kernel feature is useful for number crunching applications
336 syscalls, it's possible to isolate those applications in
|
| /linux-4.4.14/drivers/isdn/capi/ |
| D | Kconfig | 15 applications via /dev/capi20. Applications should use the
|
| /linux-4.4.14/drivers/usb/misc/sisusbvga/ |
| D | Kconfig | 22 want to support userland applications that utilize the driver's
|
| /linux-4.4.14/net/dccp/ |
| D | Kconfig | 12 for use by applications such as streaming media, Internet telephony,
|
| /linux-4.4.14/net/dccp/ccids/ |
| D | Kconfig | 24 suitable than CCID-2 for applications such streaming media where a
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | userspace-tools | 36 If you want some graphical indicators of system health look for applications
|
| D | lm95245 | 33 user-space applications, two absolute values are exported, one for each
|
| D | ucd9200 | 26 designed for non-isolated DC/DC power applications. The devices integrate
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | cs35l32.txt | 27 - cirrus,sdout-datacfg : Data configuration for dual CS35L32 applications only.
|
| /linux-4.4.14/drivers/staging/lustre/lustre/ |
| D | Kconfig | 40 applications can pass to Lustre kernel module through ioctl interface.
|
| /linux-4.4.14/Documentation/ia64/ |
| D | efirtc.txt | 11 The purpose of this driver is to supply an API for kernel and user applications
39 without necessarily impacting any of the user applications. The decoupling
|
| /linux-4.4.14/drivers/video/fbdev/omap/ |
| D | Kconfig | 29 Say Y here, if your user-space applications are capable of
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | introduction.txt | 11 applications and read security attributes from incoming network packets. It
|
| /linux-4.4.14/net/openvswitch/ |
| D | Kconfig | 18 control is useful in a wide variety of applications but is
|
| /linux-4.4.14/Documentation/misc-devices/mei/ |
| D | mei.txt | 61 simultaneous user connected applications. The Intel MEI driver
62 handles this internally by maintaining request queues for the applications.
178 2.0 and later releases in the same way that network applications do via SOAP
|
| D | mei-client-bus.txt | 8 MEI misc character device is useful for dedicated applications to send and receive
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | TODO | 6 system. It allows blind users to interact with applications on the
|
| /linux-4.4.14/drivers/staging/gs_fpgaboot/ |
| D | README | 22 used in various applications. Hardware design needs to programmed through
|
| /linux-4.4.14/net/can/ |
| D | Kconfig | 12 (NMEA2000), industrial, and medical applications.
|
| /linux-4.4.14/drivers/s390/char/ |
| D | Kconfig | 20 prompt "Support for fullscreen applications on 3270 terminals"
23 Include support for fullscreen applications on an IBM 3270 terminal.
|
| /linux-4.4.14/fs/ocfs2/ |
| D | Kconfig | 34 It cannot manage any other cluster applications.
|
| /linux-4.4.14/Documentation/RCU/ |
| D | listRCU.txt | 4 One of the best applications of RCU is to protect read-mostly linked lists
7 the list macros. This document describes several applications of RCU,
13 The best applications are cases where, if reader-writer locking were
|
| /linux-4.4.14/arch/arm64/ |
| D | Kconfig | 422 requires applications compiled with 16K (or a multiple of 16K)
430 look-up. AArch32 emulation requires applications compiled
549 This kernel feature is useful for number crunching applications
553 syscalls, it's possible to isolate those applications in
655 be unexpected results in the applications.
781 If you want to execute 32-bit userspace applications, say Y.
|
| /linux-4.4.14/fs/nfs/ |
| D | Kconfig | 59 applications on NFS clients to manipulate POSIX Access Control
65 applications to access and modify ACLs on files on the server.
|
| /linux-4.4.14/arch/m68k/ifpsp060/ |
| D | os.S | 59 | instructions for supervisor mode applications and call _copyin()/_copyout()
60 | for user mode applications.
|
| /linux-4.4.14/drivers/staging/lustre/ |
| D | README.txt | 42 (faster, for applications that require flock but do not run
|
| /linux-4.4.14/drivers/s390/block/ |
| D | Kconfig | 72 use applications written for the EER facility.
|
| /linux-4.4.14/tools/testing/selftests/futex/ |
| D | README | 11 primitives. These can be used as is in user applications or can serve as
|
| /linux-4.4.14/Documentation/arm/ |
| D | mem_alignment | 15 Now for user space applications, it is possible to configure the alignment
|
| D | IXP4xx | 11 is targeted for network applications, though it has become popular
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | net_prio.txt | 6 applications
|
| D | memory.txt | 25 a. Isolate an application or a group of applications
26 Memory-hungry applications can be isolated and limited to a smaller
778 allocation cost; based on the pressure, applications can implement
790 etc. Upon this event applications may decide to further analyze
|
| /linux-4.4.14/arch/microblaze/ |
| D | Kconfig | 117 This kernel feature is useful for number crunching applications
121 syscalls, it's possible to isolate those applications in
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | Exporting | 9 point. Local applications have a reference-counted hold on suitable
11 applications that access a filesystem via a remote filesystem protocol
|
| D | knfsd-stats.txt | 32 to zero these counters, instead applications should do their own
|
| /linux-4.4.14/net/wireless/ |
| D | Kconfig | 142 If this causes your applications to misbehave you should fix your
143 applications instead -- they need to register their network
|
| /linux-4.4.14/sound/drivers/ |
| D | Kconfig | 104 allows to connect applications using raw MIDI devices to
207 isn't recommended because many applications try to reopen
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | hvcs.txt | 35 space applications access to the system consoles of logically partitioned
212 which requires the use of applications that provide bi-directional,
225 For this reason kermit and cu are two of the recommended applications for
231 In order to ensure proper functioning of console applications one must make
237 applications that are invoked from the console that they should output
448 applications can affect the display of character control sequences.
|
| D | cxlflash.txt | 20 CXL provides a mechanism by which user space applications can
118 mode. While it is not a requirement that applications understand
|
| /linux-4.4.14/arch/hexagon/ |
| D | Kconfig | 33 performance and low power across a wide variety of applications.
|
| /linux-4.4.14/Documentation/devicetree/bindings/bus/ |
| D | imx-weim.txt | 5 wireless and mobile applications that use low-power technology.
|
| /linux-4.4.14/drivers/firewire/ |
| D | Kconfig | 63 analysis and in development of IEEE 1394 drivers, applications,
|
| /linux-4.4.14/arch/tile/ |
| D | Kconfig | 184 performance on memory-intensive applications, a page size of 64KB
229 This kernel feature is useful for number crunching applications
233 syscalls, it's possible to isolate those applications in
|
| /linux-4.4.14/drivers/nvdimm/ |
| D | Kconfig | 64 applications that rely on sector writes not being torn (a
|
| /linux-4.4.14/Documentation/input/ |
| D | userio.txt | 18 /dev/userio character device in their applications. Commands are sent to the
|
| D | gamepad.txt | 119 applications should support both and choose what is more appropriate if
|
| D | multi-touch-protocol.txt | 28 applications, the MT protocol can be implemented on top of the ST protocol
405 In order to stay compatible with existing applications, the data reported
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | axp20x.txt | 39 applications that aren't battery constrained.
|
| /linux-4.4.14/Documentation/accounting/ |
| D | delay-accounting.txt | 28 Userspace utilities, particularly resource management applications, can also
|
| /linux-4.4.14/arch/x86/boot/ |
| D | header.S | 218 # because EFI applications must be relocatable. The .reloc
|
| /linux-4.4.14/Documentation/security/ |
| D | Yama.txt | 28 For a solution, some applications use prctl(PR_SET_DUMPABLE, ...) to
|
| /linux-4.4.14/net/l2tp/ |
| D | Kconfig | 17 possible to both end-users and applications.
|
| /linux-4.4.14/arch/ |
| D | Kconfig | 17 and applications.
101 enable instrumentation applications (such as 'perf probe')
104 are hit by user-space applications.
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | README | 182 that is ignored by local server applications and non-cifs clients and that will
187 applications running on the same server as Samba.
420 unmount or reboot which can confuse some applications,
461 operation on that file. This prevent applications like WINE
500 This is necessary for certain applications that break
506 (presumably rare) applications, originally coded for
522 applications that fsync too much, at a small risk of server
561 used by some applications such as Samba and NFSv4 server to
|
| /linux-4.4.14/fs/nfsd/ |
| D | Kconfig | 52 This protocol extension allows applications on NFS clients to
|
| /linux-4.4.14/Documentation/trace/ |
| D | stm.txt | 20 master 7 channel 15, while arbitrary user applications can use masters
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | kernel.txt | 230 processes may be piped to user space applications in parallel. If
538 applications that use the old 16-bit UID/GID system calls, if the
717 There are a few legacy applications out there (such as some ancient
719 just after the end of the code+bss. These applications break when
721 non-legacy applications that would be broken this way, so for most
794 defined, so some applications might stop working. Note that this
|
| D | vm.txt | 307 applications are using mlock(), or if you are running with no swap then
378 While most applications need less than a thousand maps, certain
392 transparently without affecting any applications. But if there is
483 vast majority of applications to work correctly and provide defense in depth
|
| /linux-4.4.14/arch/powerpc/ |
| D | Kconfig | 337 Some PowerPC chips designed for embedded applications do not have
529 Note, that kernel will be able to run only those applications,
579 space applications with a non-standard binutils settings
689 This kernel feature is useful for number crunching applications
693 syscalls, it's possible to isolate those applications in
|
| /linux-4.4.14/Documentation/prctl/ |
| D | seccomp_filter.txt | 10 certain subset of userland applications benefit by having a reduced set
13 use with those applications.
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | dapm.txt | 12 DAPM is also completely transparent to all user space applications as
14 recompiling are required for user space applications. DAPM makes power
|
| /linux-4.4.14/drivers/i2c/ |
| D | Kconfig | 12 many micro controller applications and developed by Philips. SMBus,
|
| /linux-4.4.14/drivers/usb/ |
| D | Kconfig | 134 applications might not work.
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | lis3lv02d | 51 Measurement values are provided to help HW diagnostic applications to make
|
| /linux-4.4.14/fs/ncpfs/ |
| D | Kconfig | 38 special applications which are able to utilize this locking scheme.
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | user_mad.txt | 113 compatibility with older applications, this new layout will not be used
|
| /linux-4.4.14/arch/avr32/ |
| D | Kconfig | 22 designed for cost-sensitive embedded applications, with particular
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 3.Early-stage | 19 sought a way to run applications without dropouts or other artifacts caused
22 framework; this module could be configured to give specific applications
|
| /linux-4.4.14/Documentation/x86/ |
| D | intel_mpx.txt | 28 No source changes are required for applications, just a recompile.
147 allocation syscall. This can be done for small, constrained applications.
|
| /linux-4.4.14/Documentation/block/ |
| D | data-integrity.txt | 91 Generally Linux/POSIX applications are agnostic to the intricacies of
121 This also means that applications such as fsck and mkfs will need
|
| /linux-4.4.14/arch/s390/ |
| D | Kconfig | 344 executing 31 bit applications. It is safe to say "Y".
698 This kernel feature is useful for number crunching applications
702 syscalls, it's possible to isolate those applications in
|
| /linux-4.4.14/arch/sparc/ |
| D | Kconfig | 241 This kernel feature is useful for number crunching applications
245 syscalls, it's possible to isolate those applications in
|
| /linux-4.4.14/drivers/char/ |
| D | Kconfig | 204 This is most useful for applications, as yet unwritten, which
532 If you say Y here, user applications will be able to mmap
544 registers for applications that require it.
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | Sound-FAQ | 88 You might also dig around in the *.ini files of the Windows applications.
|
| /linux-4.4.14/drivers/input/ |
| D | Kconfig | 14 it to be available to applications. This includes standard PS/2
|
| /linux-4.4.14/arch/cris/arch-v10/drivers/ |
| D | Kconfig | 42 Try 0-3 for low latency applications. Approx 5 for high load
43 applications (e.g. PPP). Maybe this should be more adaptive some
|
| /linux-4.4.14/scripts/ |
| D | spelling.txt | 98 applictions||applications
99 appplications||applications
|
| /linux-4.4.14/init/ |
| D | Kconfig | 670 applications that do not have any CPU-bound threads.
672 Some real-time applications might not have a single real-time
1237 desktop applications. Task group autogeneration is currently based
1501 run glibc-based applications correctly.
1575 by some high performance threaded applications. Disabling
1583 applications to advise the kernel about their future memory or file
1585 applications use these syscalls, you can disable this option to save
1656 kernel or applications. These registers can also trigger interrupts
|
| /linux-4.4.14/sound/core/ |
| D | Kconfig | 53 devices or applications together.
|
| /linux-4.4.14/arch/sh/boards/ |
| D | Kconfig | 341 intended for embedded applications.
|
| /linux-4.4.14/arch/sh/ |
| D | Kconfig | 656 This kernel feature is useful for number crunching applications
660 syscalls, it's possible to isolate those applications in
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | watchdog-api.txt | 172 real world applications include external monitoring pins that will trigger
|
| /linux-4.4.14/Documentation/crypto/ |
| D | async-tx-api.txt | 171 accommodate assumptions made by applications using the async_tx API:
|