| /linux-4.4.14/Documentation/virtual/ |
| D | paravirt_ops.txt | 8 hypervisors. It allows each hypervisor to override critical operations and
12 pv_ops provides a set of function pointers which represent operations
15 time by enabling binary patching of the low-ops critical operations
18 pv_ops operations are classified into three categories:
21 These operations correspond to high level functionality where it is
25 Usually these operations correspond to low level critical instructions. They
|
| /linux-4.4.14/Documentation/arm/ |
| D | firmware.txt | 1 Interface for registering and calling firmware-specific operations for ARM.
8 operations and call them when needed.
10 Firmware operations can be specified by filling in a struct firmware_ops
19 There is a default, empty set of operations provided, so there is no need to
20 set anything if platform does not require firmware operations.
31 Example of registering firmware operations:
50 /* other operations not available on platformX */
|
| D | cluster-pm-race-avoidance.txt | 5 cluster setup and teardown operations and to manage hardware coherency
25 involves performing potentially destructive operations affecting a group
28 cluster-level operations are only performed when it is truly safe to do
189 operations required to achieve this (such as cleaning data
302 other operations (such as cache invalidation) which are required
353 To avoid wasteful unnecessary teardown operations, the outbound
392 unnecessary teardown and setup operations in situations where
411 The CPU which performs cluster tear-down operations on the outbound side
451 arch/arm/common/mcpm_head.S (low-level inbound CPU operations) and
|
| D | swp_emulation | 25 cause programs that perform SWP operations to uncached memory to deadlock, as
|
| D | kernel_user_helpers.txt | 6 with some operations which require kernel help because of unimplemented
21 overhead to such minimalistic operations.
63 fprintf(stderr, "can't do atomic operations, kernel too old\n");
|
| D | Interrupts | 50 the various operations (maybe this'll change to a better name).
51 This structure has the following operations:
|
| /linux-4.4.14/Documentation/ |
| D | this_cpu_ops.txt | 1 this_cpu operations
4 this_cpu operations are a way of optimizing access to per cpu
10 this_cpu operations add a per cpu variable offset to the processor
20 Read-modify-write operations are of particular interest. Frequently
35 (remote write operations) of local RMW operations via this_cpu_*.
37 The main use of the this_cpu operations has been to optimize counter
38 operations.
40 The following this_cpu() operations with implied preemption protection
41 are defined. These operations can be used without worrying about
61 Inner working of this_cpu operations
[all …]
|
| D | local_ops.txt | 6 This document explains the purpose of the local atomic operations, how
11 Note that local_t based operations are not recommended for general kernel use.
12 Please use the this_cpu operations instead unless there is really a special purpose.
13 Most uses of local_t in the kernel have been replaced by this_cpu operations.
14 this_cpu operations combine the relocation with the local_t like semantics in
18 * Purpose of local atomic operations
20 Local atomic operations are meant to provide fast and highly reentrant per CPU
21 counters. They minimize the performance cost of standard atomic operations by
30 Local atomic operations only guarantee variable modification atomicity wrt the
40 It can be done by slightly modifying the standard atomic operations : only
[all …]
|
| D | clk.txt | 13 gating, rate adjustment, muxing or other operations. This framework is
21 drivers/clk/clk.c. Finally there is struct clk_ops, whose operations
61 the operations defined in clk.h:
155 must never be included from the code which implements the operations for
166 To take advantage of your data you'll need to support valid operations
246 .disable and .is_enabled operations. Those operations are thus not allowed to
250 The prepare lock is a mutex and is held across calls to all other operations.
251 All those operations are allowed to sleep, and calls to the corresponding API
254 This effectively divides operations in two groups from a locking perspective.
256 Drivers don't need to manually protect resources shared between the operations
[all …]
|
| D | atomic_ops.txt | 25 The first operations to implement for atomic_t's are the initializers and
35 The initializer is atomic in that the return values of the atomic operations
56 The setting is atomic in that the return values of the atomic operations by
68 values initialized or modified with the interface operations if a proper
71 interface operations. atomic_read does not guarantee that the runtime
174 locks, or atomic operations if variable a can change at runtime!
206 the operation. It must be done such that all memory operations before
265 with the given old and new values. Like all atomic_xxx operations,
267 other accesses of *v are performed through atomic_xxx operations.
303 It makes sure that all memory operations preceding the atomic_dec()
[all …]
|
| D | memory-barriers.txt | 12 - Device operations.
47 - Atomic operations.
101 Each CPU executes a program that generates memory access operations. In the
103 perform the memory operations in any order it likes, provided program causality
108 So in the above diagram, the effects of the memory operations performed by a
109 CPU are perceived by the rest of the system as the operations cross the
199 the CPU will issue the following memory operations:
214 the CPU will only issue the following sequence of memory operations:
321 As can be seen above, independent memory operations are effectively performed
327 ordering over the memory operations on either side of the barrier.
[all …]
|
| D | sgi-ioc4.txt | 29 IOC4 function probe and remove operations isn't precisely the same
30 as PCI device probe and remove operations, but is logically the
|
| D | dma-buf-sharing.txt | 18 - implements and manages operations[1] for the buffer
32 dma-buf operations for device dma only
50 connects its own private buffer data, provides implementation for operations
104 for scatterlist operations. It will optionally call the 'attach' dma_buf
132 It is one of the buffer operations that must be implemented by the exporter.
202 Bracketing of DMA access with {map,unmap}_dma_buf operations is essential
220 and then allow further {map,unmap}_dma_buf operations from any buffer-user
236 - fallback operations, e.g. if the devices is connected to a usb bus and the
405 synchronization at fault time with outstanding device operations.
|
| D | ramoops.txt | 27 depends on atomic operations. At least on ARM, pgprot_noncached causes the
28 memory to be mapped strongly ordered, and atomic operations on strongly ordered
|
| D | cachetlb.txt | 49 page table operations such as what happens during
64 Primarily, this is used for munmap() type operations.
153 page table operations such as what happens during exit and exec.
162 page table operations such as what happens during fork.
176 Primarily, this is used for munmap() type operations.
341 Any necessary cache flushing or other coherency operations
|
| D | DMA-ISA-LPC.txt | 89 using claim_dma_lock(). The reason is that some DMA operations are
95 controller that is used for the non-atomic operations. As long as you
|
| D | kernel-per-CPU-kthreads.txt | 82 3. Once your application has started, prevent CPU-hotplug operations
89 3. Once your application has started, prevent CPU-hotplug operations
96 3. Once your application has started, prevent CPU-hotplug operations
245 avoid initiating any CPU hotplug operations on this CPU. This is
|
| D | phy.txt | 63 phy_ops is a set of function pointers for performing PHY operations such as
139 phy_pm_runtime_forbid for performing PM operations.
|
| D | adding-syscalls.txt | 18 - If the operations involved can be made to look like a filesystem-like
22 - If the new functionality involves operations where the kernel notifies
26 - However, operations that don't map to read(2)/write(2)-like operations
436 multiplexor (socketcall) operations. If your new system call is analogous to
|
| /linux-4.4.14/Documentation/crypto/ |
| D | async-tx-api.txt | 9 3.2 Supported operations
31 the API will fit the chain of operations to the available offload
47 operations to be submitted, like xor->copy->xor in the raid5 case. The
59 3.2 Supported operations:
79 operations complete. When an application needs to submit a chain of
80 operations it must guarantee that the descriptor is not automatically recycled
85 1/ setting the ASYNC_TX_ACK flag if no child operations are to be submitted
92 async_<operation> call. Offload engine drivers batch operations to
95 automatically issues pending operations. An application can force this
105 chains and issuing pending operations.
[all …]
|
| D | asymmetric-keys.txt | 24 associated with the key and provides operations to describe and destroy it.
31 operations using that key. In such a case, the asymmetric key would then
37 subtype of the key and define the operations that can be done on that key.
110 The operations defined upon a key are:
114 Other operations are possible (such as encryption) with the same key data
165 Asymmetric keys have a subtype that defines the set of operations that can be
194 There are a number of operations defined by the subtype:
211 Optional. These are the entry points for the key usage operations.
|
| /linux-4.4.14/Documentation/devicetree/bindings/dma/ |
| D | ste-dma40.txt | 60 bidirectional, i.e. the same for RX and TX operations:
113 51: memcpy TX (to be used by the DMA driver for memcpy operations)
118 56: memcpy (to be used by the DMA driver for memcpy operations)
119 57: memcpy (to be used by the DMA driver for memcpy operations)
120 58: memcpy (to be used by the DMA driver for memcpy operations)
121 59: memcpy (to be used by the DMA driver for memcpy operations)
122 60: memcpy (to be used by the DMA driver for memcpy operations)
|
| D | mv-xor.txt | 17 - dmacap,memcpy to indicate that the XOR channel is capable of memcpy operations
18 - dmacap,memset to indicate that the XOR channel is capable of memset operations
19 - dmacap,xor to indicate that the XOR channel is capable of xor operations
|
| D | apm-xgene-dma.txt | 21 - dma-coherent : Present if dma operations are coherent
|
| D | arm-pl330.txt | 13 - dma-coherent : Present if dma operations are coherent
|
| /linux-4.4.14/Documentation/networking/ |
| D | nfc.txt | 20 responsible for providing an interface to control operations and low-level
23 The control operations are available to userspace via generic netlink.
34 | data exchange | operations
69 The userspace interface is divided in control operations and low-level data
74 Generic netlink is used to implement the interface to the control operations.
75 The operations are composed by commands and events, all listed below:
98 All polling operations requested through one netlink socket are stopped when
|
| D | dm9000.txt | 97 The IO should be done with 8bit operations.
101 The IO should be done with 16bit operations.
105 The IO should be done with 32bit operations.
|
| D | ipv6.txt | 19 IPv6 addresses or operations are desired.
|
| D | altera_tse.txt | 46 The driver limits PHY operations to 10/100Mbps, and has not yet been fully
84 using NAPI for receive operations. Interrupt mitigation is not yet supported
85 for transmit operations, but will be added in a future maintenance release.
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | debugfs-pfo-nx-crypto | 33 - The total number of AES operations submitted to the hardware.
39 - The total number of SHA-256 operations submitted to the hardware.
45 - The total number of SHA-512 operations submitted to the hardware.
|
| D | sysfs-wusb_cbaf | 9 The sequence of operations should be:
|
| D | sysfs-class-mtd | 168 ecc_strength, -EUCLEAN is never returned by the read operations.
194 these failures are associated with failed read operations.
|
| D | sysfs-devices-memory | 8 operations.
|
| D | sysfs-block | 131 workloads where a high number of I/O operations is
151 Standard I/O elevator operations include attempts to
|
| /linux-4.4.14/Documentation/arm/VFP/ |
| D | release-notes.txt | 17 The operations which have been tested with this package are:
39 Other operations which have been tested by basic assembly-only tests
49 The combination operations have not been tested:
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | operations.txt | 24 FS-Cache has an asynchronous operations handling facility that it uses for its
25 data storage and retrieval routines. Its operations are represented by
30 and FS-Cache will create operations and pass them off to the appropriate cache
76 operations:
82 This is, for example, used in read operations for calling readpages() on
122 Furthermore, operations may be one of two types:
132 operations running at the same time.
162 The operation manager will defer operations on an object that is still
|
| D | object.txt | 111 (3) Normal running: states that allow netfs operations on objects to proceed
184 read operations, no matter whether the file is yet cached. If not yet
185 cached, read operations will be immediately rejected with ENODATA until
201 operations the netfs has queued for an object. If creation failed, the
210 A transient state in which pending operations are started, child objects
222 discards all pending read, write and attribute change operations as it is
|
| D | netfs-api.txt | 37 (14) Miscellaneous cookie operations
342 filling in the index entry by calling the operations pointed to by def.
438 to the caller. The attribute adjustment excludes read and write operations.
787 There are a number of operations that can be used to control cookies:
794 These operations permit data cookies to be pinned into the cache and to
867 cancelled and discarded. Some future operations will be rejected until the
868 cache has had a chance to insert a barrier in the operations queue. After
869 that, operations will be queued again behind the invalidation operation.
875 to have reached a point at which it can start submitting ordinary operations
897 Furthermore, if this bit is set, releasepage() and invalidatepage() operations
[all …]
|
| D | backend-api.txt | 31 (*) "ops" is a pointer to the table of operations that the backend supports on
121 cache operations.
166 various asynchronous operations that need to be done as part of driving
219 The cache backend provides FS-Cache with a table of operations that can be
385 storage and retrieval operations from the netfs are excluded during the
537 has been called, only resource dissociation operations (object and page
571 one or more pending operations to start running.
|
| D | fscache.txt | 362 OPS Number of outstanding operations on this object
363 OOP Number of outstanding child object management operations
365 EX Number of outstanding exclusive operations
366 READS Number of outstanding read operations
|
| /linux-4.4.14/net/rds/ |
| D | Kconfig | 15 This transport supports RDMA operations.
22 This transport does not support RDMA operations.
|
| /linux-4.4.14/Documentation/scsi/ |
| D | ufs.txt | 60 * Device manager: It handles device level operations and device
61 configuration operations. Device level operations mainly involve
62 device power management operations and commands to Interconnect
73 manager for device level operations. These device level operations
|
| D | bnx2fc.txt | 65 Refer to fcoeadm manpage for more information on fcoeadm operations to
|
| D | cxgb3i.txt | 8 (DDP) where the hardware handles the expensive byte touching operations, such
|
| D | ncr53c8xx.txt | 82 18.2 NCR chip in Big Endian mode of operations
128 the proc SCSI file system read / write operations.
183 Profiling information: read operations from the proc SCSI file system
184 Control commands: write operations to the proc SCSI file system
434 Control commands can be sent to the driver with write operations to
481 simple: use SIMPLE TAG for all operations (read and write)
482 ordered: use ORDERED TAG for all operations
484 SIMPLE TAG for read operations
485 ORDERED TAG for write operations
593 even while performing long SCSI operations.
[all …]
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | watchdog-kernel-api.txt | 19 (operations) that control the watchdog timer (WDT).
74 * ops: a pointer to the list of watchdog operations that the watchdog supports.
91 The list of watchdog operations is defined as:
95 /* mandatory operations */
98 /* optional operations */
109 driver's operations. This module owner will be used to lock the module when
114 is not enough and a driver also needs to define the ref and unref operations to
127 Some operations are mandatory and some are optional. The mandatory operations
142 all other routines/operations are optional. They only need to be provided if
143 they are supported. These optional routines/operations are:
[all …]
|
| /linux-4.4.14/arch/unicore32/mm/ |
| D | Kconfig | 34 Say Y here to disable the data cache line operations.
40 Say Y here to disable the TLB single entry operations.
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | spufs.txt | 35 the operations supported on regular file systems. This list details the
36 supported operations and the deviations from the behaviour in the
41 All files support the access(2) and stat(2) family of operations, but
47 possible operations, e.g. read access on the wbox file.
55 data in the address space of the SPU. The possible operations on an
74 operations on an open mbox file are:
88 operations on an open ibox file are:
111 operations on an open wbox file are: write(2) If a count smaller than
135 operations on an open *box_stat file are:
173 The possible operations on an open npc, decr, decr_status,
[all …]
|
| D | directory-locking | 1 Locking scheme used for directory operations is based on two
9 For our purposes all operations fall in 5 classes:
68 (Proof: all operations but renames take lock on at most one
91 It means that one of the operations is cross-directory rename.
107 These operations are guaranteed to avoid loop creation. Indeed,
121 also preserved by all operations (cross-directory rename on a tree that would
|
| D | afs.txt | 173 No other cell database operations are available at this time.
180 Secure operations are initiated by acquiring a key using the klog program. A
207 not acquired then all operations will be governed by the anonymous user parts
210 If a key is acquired, then all AFS operations, including mounts and automounts,
215 socket), then the operations on the file will be made with key that was used to
|
| D | gfs2-glocks.txt | 36 operations. The glocks are basically a lock plus some routines which deal
46 These rules are implemented using the various glock operations which
50 Table of glock operations and per type constants:
83 Locking rules for glock operations:
108 4. Rgrp glock(s) (for (de)allocation operations)
109 5. Transaction glock (via gfs2_trans_begin) for non-read operations
|
| D | Locking | 8 Thing currently missing here: socket operations. Alexey?
108 of the locking scheme for directory operations.
241 "sync". These are quite different operations and the behaviour may differ
294 sync operations. The address_space should start I/O against at least
334 backing swapspace. The swapspace operations will be proxied to the
335 address space operations.
492 ->setlease operations should call generic_setlease() before or after setting
504 These operations are intended to be more or less wrapping functions that ensure
505 a proper locking wrt the filesystem and call the generic quota operations.
517 operations.
|
| D | autofs4-mount-control.txt | 2 Miscellaneous Device control operations for the autofs4 kernel module
13 operations. Using a file descriptor gives ioctl operations access to
14 autofs specific information stored in the super block. The operations
19 file descriptor for these operations if we don't already have one open.
106 on the mount point for control operations. The references held by the
120 existing ioctl interface and add new operations to provide this
229 The device node ioctl operations implemented by this interface are:
265 The close call is included in the implemented operations largely for
|
| D | exofs.txt | 147 operations and is used as long as the object remains in memory.
149 * Async OSD operations are used whenever possible, but the target may execute
150 them out of order. The operations that concern us are create, delete,
152 operations should execute in the order written, and we need to prevent them
|
| D | ubifs.txt | 18 2 MTD devices support 3 main operations - read from some offset within an
20 eraseblock. Block devices support 2 main operations - read a whole
40 they have read/write/erase operations, but UBI devices are devoid of
|
| D | path-lookup.txt | 28 because of the locks and atomic operations required for every dentry element
100 Back to the rename case. In usual RCU protected lists, the only operations that
166 lookup operations. If a file is renamed from 'A' to 'B', a lookup must only
191 Also important is to avoid performing any destructive operations (pretty much:
194 Avoiding destructive or changing operations means we can easily unwind from
200 it in any way. This returned dentry can be used for subsequent operations,
219 eg. if the filesystem must sleep or perform non trivial operations, rcu-walk
288 operations such as creates and unlinks are not uncommon.
|
| D | ocfs2.txt | 46 intr (*) Allow signals to interrupt cluster operations.
48 operations.
|
| D | 00-INDEX | 16 - info on device control operations for autofs4 module.
45 - info about the locking scheme used for directory operations.
|
| D | fuse.txt | 35 The user who is performing filesystem operations.
109 With this option the maximum size of read operations can be set.
148 Interrupting filesystem operations
255 exact sequence and timing of operations performed. This
|
| D | debugfs.txt | 48 resulting inode structure, and fops is a set of file operations which
50 operations should be provided; others can be included as needed. Again,
65 In a number of cases, the creation of a set of file operations is not
|
| D | seq_file.txt | 38 * A set of canned file_operations which implement most operations on
222 creation of a set of file_operations which implement the operations on that
223 file. The seq_file interface provides a set of canned operations which do
275 The other operations of interest - read(), llseek(), and release() - are
|
| D | porting | 97 BKL is also moved from around sb operations. BKL should have been shifted into
144 Briefly it allows for the definition of decode_fh and encode_fh operations
365 atomic operations and scalability hazards on dentries and inodes (see
447 in your dentry operations instead.
|
| /linux-4.4.14/Documentation/rapidio/ |
| D | tsi721.txt | 7 It supports maintenance read and write operations, inbound and outbound RapidIO
29 Depending on system requirements RapidIO DMA operations can be included/excluded
41 1.1.0 - DMA operations re-worked to support data scatter/gather lists larger
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/4xx/ |
| D | emac.txt | 34 operations.
37 operations.
45 - phy-mode : string, mode of operations of the PHY interface.
75 operations (if absent the value is the same as
78 operations (if absent the value is the same as
|
| /linux-4.4.14/Documentation/laptops/ |
| D | disk-shock-protection.txt | 24 a shock protection facility. The idea is to stop all I/O operations on
43 of the respective drive off the platter and block all I/O operations
62 /dev/sda and stop all I/O operations for five seconds:
82 been issued to a device successfully, all I/O operations on the
87 operations on that port will be deferred until the timeout specified
104 I/O operations on that drive (and the reset itself) will be delayed
|
| /linux-4.4.14/Documentation/xtensa/ |
| D | atomctl.txt | 17 Memory controller we let it to the atomic operations internally while
19 operations.
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | changesets.txt | 21 All the change operations are recorded in the of_changeset 'entries'
31 5. mutex_unlock(of_mutex) - All operations complete, release the mutex
|
| /linux-4.4.14/Documentation/filesystems/pohmelfs/ |
| D | design_notes.txt | 27 * Transactions support. Full failover for all operations.
49 Only a few non-performance critical operations use the write-through cache and
59 operations (like lookups or directory listings) between them according to IO priorities.
71 crypto operations and send the resulting data to server or submit it up the stack. This number
|
| D | info.txt | 37 Default is 2, or no threads if crypto operations are not supported.
46 If specified, mount will fail if the server does not support requested crypto operations.
47 By default mount will disable non-matching crypto operations.
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | DPCM.txt | 95 3) DPCM runs the PCM trigger(stop), hw_free(), shutdown() operations on DAI0
104 and then DPCM will take care of managing the DAI PCM operations to either bring
117 2) Define any FE/BE PCM operations.
223 2 FE/BE PCM operations
226 The BE above also exports some PCM operations and a "fixup" callback. The fixup
331 graph. Control is then carried out by the FE as regular PCM operations.
366 valid path and then calls the PCM operations to start the link. DAPM will also
367 call the appropriate PCM operations to disable the DAI when the path is no
|
| D | codec.txt | 15 4) Codec audio operations
32 PCM capabilities and operations. This struct is exported so that it can be
114 The codec driver also supports the following ALSA PCM operations:-
|
| D | platform.txt | 11 The platform DMA driver optionally supports the following ALSA operations:-
|
| /linux-4.4.14/arch/arm/mach-vexpress/ |
| D | dcscb_setup.S | 33 2: @ Implementation-specific local CPU setup operations should go here,
|
| /linux-4.4.14/Documentation/dmaengine/ |
| D | provider.txt | 8 operations.
80 support other kind of transfers or memory operations that dmaengine
87 async TX API, to offload operations such as memory copy, XOR,
163 - The device is able to perform XOR operations on memory areas
235 Device operations
240 operations we were able to perform.
313 - This call is mandatory for slave operations only. This should NOT be
314 set or expected to be set for memcpy operations.
316 operations only and not for memcpy ones.
339 - Makes sure that dependent operations are run before marking it
[all …]
|
| D | client.txt | 80 Various types of operations could be expressed by setting
117 submission so it is important that these two operations are closely
122 routines cannot submit any new operations, this is not the
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | nfs41-server.txt | 28 the operations that are mandatory to implement (REQ), optional
29 (OPT), and NFSv4.0 operations that are required not to implement (MNI)
30 in minor version 1. The first column indicates the operations that
39 I Implemented NFSv4.1 operations.
|
| D | rpc-server-gss.txt | 30 unwarranted. However GSSAPI operations are fundementally separable in 2
|
| /linux-4.4.14/drivers/staging/fsl-mc/ |
| D | README.txt | 72 The MC mediates operations such as create, discover,
73 connect, configuration, and destroy. Fast-path operations
170 is provided along with a summary of the kinds of operations the object
191 packets and do hardware buffer pool management operations. For
193 each CPU to perform simultaneous enqueue/dequeue operations.
194 -mmio regions: queue operations, buffer mgmt
340 -hardware queuing operations (enqueue and dequeue of data)
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-bench.txt | 32 (executing 1000000 pipe operations between two tasks)
120 (executing 1000000 pipe operations between two tasks)
127 (executing 1000 pipe operations between two tasks)
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | firewire-cdev | 42 Due to the different scope of operations and in order to let
44 operations are restricted to /dev/fw* files that are associated
55 The following file operations are supported:
|
| D | sysfs-firmware-opal-elog | 60 operations (currently just acknowledge).
|
| /linux-4.4.14/drivers/staging/clocking-wizard/ |
| D | TODO | 4 - support for set_rate() operations (may benefit from Stephen Boyd's
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | calxeda-xgmac.txt | 10 - dma-coherent : Present if dma operations are coherent
|
| D | keystone-netcp.txt | 7 accelerator (PA) module to perform packet classification operations such as
8 header matching, and packet modification operations such as checksum
10 capable of performing IPSec operations on ingress/egress packets.
58 - dma-coherent: Present if dma operations are coherent
|
| D | snps,dwc-qos-ethernet.txt | 16 - dma-coherent: Present if dma operations are coherent
|
| D | amd-xgbe.txt | 31 - dma-coherent: Present if dma operations are coherent
|
| /linux-4.4.14/Documentation/devicetree/bindings/pci/ |
| D | arm,juno-r1-pcie.txt | 10 in a manner that makes the DMA operations to appear coherent to the CPUs.
|
| D | hisilicon-pcie.txt | 21 - dma-coherent: Present if DMA operations are coherent.
|
| D | xgene-pci.txt | 24 - dma-coherent: Present if dma operations are coherent
|
| /linux-4.4.14/Documentation/devicetree/bindings/crypto/ |
| D | amd-ccp.txt | 11 - dma-coherent: Present if dma operations are coherent
|
| D | mv_cesa.txt | 20 - marvell,crypto-sram-size: SRAM size reserved for crypto operations, if not
|
| D | marvell-cesa.txt | 29 - marvell,crypto-sram-size: SRAM size reserved for crypto operations, if not
|
| /linux-4.4.14/Documentation/devicetree/bindings/xillybus/ |
| D | xillybus.txt | 11 - dma-coherent: Present if DMA operations are coherent
|
| /linux-4.4.14/drivers/staging/unisys/ |
| D | TODO | 10 - upgrade/remove deprecated workqueue operations
|
| /linux-4.4.14/Documentation/power/regulator/ |
| D | regulator.txt | 16 This will register the regulator's capabilities and operations to the regulator
|
| /linux-4.4.14/security/tomoyo/ |
| D | Kconfig | 48 operations which can lead to the hijacking of the boot sequence are
51 only operations needed for mounting a partition which contains the
|
| /linux-4.4.14/Documentation/i2c/ |
| D | i2c-stub | 19 operations. This allows for continuous byte reads like those supported by
27 SMBus block operations. Writes can be partial. Block read commands always
|
| D | smbus-protocol | 20 Below is a list of SMBus protocol operations, and the functions executing
22 don't match these function names. For some of the operations which pass a
|
| /linux-4.4.14/Documentation/frv/ |
| D | atomic-ops.txt | 6 instruction. Unfortunately, this alone can't be used to implement the following operations:
16 On such CPUs, the standard way of emulating such operations in uniprocessor mode is to disable
34 (*) All atomic operations can then be broken down into the following algorithm:
|
| D | README.txt | 51 A description of how the FR-V kernel's atomic operations work.
|
| /linux-4.4.14/drivers/crypto/ccp/ |
| D | Kconfig | 8 which can be used to offload encryption operations such as SHA,
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-gpio.txt | 12 - i2c-gpio,delay-us: delay between GPIO operations (may depend on each platform)
|
| /linux-4.4.14/scripts/coccinelle/tests/ |
| D | doubletest.cocci | 1 /// Find &&/|| operations that include the same argument more than once
|
| D | doublebitand.cocci | 1 /// Find bit operations that include the same argument more than once
|
| /linux-4.4.14/drivers/md/bcache/ |
| D | Kconfig | 26 operations that get stuck.
|
| /linux-4.4.14/Documentation/power/ |
| D | notifiers.txt | 4 There are some operations that subsystems or drivers may want to carry out
44 operations performed for PM_SUSPEND_PREPARE should be reversed for
|
| D | userland-swsusp.txt | 16 release(), read(), and write() operations as well as several ioctl()
156 file system operations (including reads) on the file systems
159 mounted at that time and perform some operations on it (eg.
167 be mounted before suspend and SHOULD NOT attempt to perform any operations
|
| D | opp.txt | 66 operations until that OPP could be re-enabled if possible.
80 care to refresh the cpufreq table in cases of these operations.
86 intensive operations on data structure as the OPP library caters to.
95 and other contexts that prevent blocking functions in RCU or mutex operations
343 Overall, in a simplistic view, the data structure operations is represented as
|
| D | drivers-testing.txt | 11 cases involves slightly different operations and different interactions with
|
| D | s2ram.txt | 69 hardware during resume operations where a value can be set that will
|
| D | pci.txt | 72 standard interface for performing various operations related to power
297 provided by PCI device drivers. They also perform power management operations
346 however, this functionality is limited to a few basic operations carried out
712 In addition to that the prepare() callback may carry out some operations
727 put it into a low-power state. All of these operations can very well be taken
730 However, in some rare case it is convenient to carry out these operations in
741 operations relying on the driver's ability to handle interrupts should be
752 suspend_noirq() can carry out operations that would cause race conditions to
821 operations that might race with the interrupt handler.
826 it should only be used for performing operations that would lead to race
[all …]
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | overview.txt | 15 and operations into globally accessible data structures.
32 not every bus is able to support all such operations, although most
33 buses support most of those operations.
|
| D | porting.txt | 119 This allows the compiler to verify type-safety of the operations
229 of operations that the driver model core may call.
281 struct device_driver defines a set of operations that the driver model
282 core calls. Most of these operations are probably similar to
283 operations the bus already defines for drivers, but taking different
|
| /linux-4.4.14/arch/arm/firmware/ |
| D | Kconfig | 18 active, requiring some core operations to be performed by the secure
|
| /linux-4.4.14/drivers/dma/bestcomm/ |
| D | Kconfig | 16 If you want to use drivers that require DMA operations,
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | user_verbs.txt | 18 management operations via the /dev/infiniband/uverbsN character
19 devices. Fast path operations are typically performed by writing
|
| /linux-4.4.14/net/rxrpc/ |
| D | Kconfig | 17 This module at the moment only supports client operations and is
|
| /linux-4.4.14/Documentation/virtual/kvm/devices/ |
| D | s390_flic.txt | 6 pending interrupts. FLIC performs operations on this list.
81 id specifies the adapter and type the operation. The supported operations
|
| /linux-4.4.14/arch/arm/include/asm/ |
| D | page.h | 107 #error Unknown user operations model
|
| /linux-4.4.14/scripts/coccinelle/api/ |
| D | simple_open.cocci | 2 /// and replace file operations references to the function
|
| /linux-4.4.14/Documentation/ptp/ |
| D | ptp.txt | 14 + Basic clock operations
46 implement the basic clock operations.
|
| /linux-4.4.14/Documentation/arm/nwfpe/ |
| D | README | 22 The floating point operations are based on SoftFloat Release 2, by
27 All operations required by the standard are implemented, except for
|
| D | README.FPE | 72 Dyadic operations:
99 Monadic operations:
|
| /linux-4.4.14/Documentation/locking/ |
| D | rt-mutex.txt | 40 RT-mutexes are optimized for fastpath operations and have no internal
42 without waiters. The optimized fastpath operations require cmpxchg
|
| D | spinlocks.txt | 22 (5) LOCK operations.
23 (6) UNLOCK operations.
53 NOTE! reader-writer locks require more atomic memory operations than
|
| D | locktorture.txt | 77 refuse to do any CPU-hotplug operations regardless of
81 operations. This would normally only be used when
|
| /linux-4.4.14/Documentation/accounting/ |
| D | cgroupstats.txt | 6 interface. A new set of cgroup operations are registered with commands
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | brcm,bcm3380-l2-intc.txt | 11 - no atomic set/clear operations
|
| D | brcm,bcm7038-l1-intc.txt | 16 - Atomic mask/unmask operations
|
| D | brcm,bcm7120-l2-intc.txt | 18 - no atomic set/clear operations
|
| /linux-4.4.14/Documentation/spi/ |
| D | spi-sc18is602 | 30 to initiate longer transfers will fail with -EINVAL. EEPROM read operations and
|
| D | spidev | 72 Normal open() and close() operations on /dev/spidevB.D files work as you
75 Standard read() and write() operations are obviously only half-duplex, and
76 the chipselect is deactivated between those operations. Full-duplex access,
|
| /linux-4.4.14/drivers/block/ |
| D | sunvdc.c | 72 u64 operations; member
240 pkt->tag.stype, pkt->operations, in vdc_handle_attr()
265 port->operations = pkt->operations; in vdc_handle_attr()
548 if (!(((u64)1 << (u64)op) & port->operations)) in generic_request()
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | soc-camera.txt | 71 /* The rest of host operations are optional */
81 .get_formats and, possibly, a .put_formats operations. See below for more
83 respective V4L2 operations.
|
| D | videobuf | 26 scatter/gather DMA operations.
30 buffers are just as hard to use for DMA operations, but they can be
133 File operations
235 ioctl() operations
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | cpuid.txt | 36 || || on PIO operations.
|
| D | hypercalls.txt | 50 Purpose: Support MMU operations such as writing to PTE,
|
| /linux-4.4.14/Documentation/devicetree/bindings/iommu/ |
| D | arm,smmu-v3.txt | 32 - dma-coherent : Present if DMA operations made by the SMMU (page
|
| /linux-4.4.14/Documentation/devicetree/bindings/ata/ |
| D | sata_highbank.txt | 14 - dma-coherent : Present if dma operations are coherent
|
| D | ahci-platform.txt | 28 - dma-coherent : Present if dma operations are coherent
|
| D | apm-xgene.txt | 27 - dma-coherent : Present if dma operations are coherent
|
| /linux-4.4.14/drivers/scsi/osd/ |
| D | Kconfig | 39 operations.
|
| /linux-4.4.14/fs/ubifs/ |
| D | Kconfig | 47 which means that file-system read operations will cause writes (inode atime
|
| /linux-4.4.14/arch/metag/lib/ |
| D | memcpy.S | 108 ! Calculate the bit offsets required for the shift operations necesssary
136 ! Calculate the bit offsets required for the shift operations necesssary
|
| /linux-4.4.14/Documentation/RCU/ |
| D | rcu.txt | 5 operations into two parts, one that prevents anyone from seeing the data
22 barriers. The fact that these operations are quite expensive
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | lis3lv02d | 43 used during normal operations. Position data is not corrupted during selftest
59 from the device. It supports blocking operations, poll/select and
|
| /linux-4.4.14/Documentation/PCI/ |
| D | pci-error-recovery.txt | 49 "resume normal operations" event is sent out.
189 start operations again, only to peek/poke at the device, extract diagnostic
191 reset or some such, but not restart operations. This callback is made if
211 normal driver operations again. There is no
242 The driver is not supposed to restart normal driver I/O operations
298 Drivers should not restart normal I/O processing operations
362 memory and remove itself from kernel operations, much as it would
|
| D | pci-iov-howto.txt | 40 PCI SRIOV core support ensures that enable/disable operations are
|
| /linux-4.4.14/Documentation/arm64/ |
| D | booting.txt | 158 cache maintenance by VA rather than set/way operations.
160 operations must be configured and may be enabled.
162 operations (not recommended) must be configured and disabled.
173 initialisation to enable the receiving of maintenance operations on
|
| /linux-4.4.14/tools/thermal/tmon/ |
| D | README | 19 normal operations.
|
| /linux-4.4.14/arch/arm/mm/ |
| D | Kconfig | 140 instruction sequences for cache and TLB operations. Curiously,
701 trylock() operations with the assumption that the code will not
710 perform SWP operations to uncached memory to deadlock.
770 To support such cache operations, it is efficient to know the size
856 cache maintenance operations and the dma_{map,unmap}_area()
865 processors, if cache maintenance operations are not broadcast
919 bool "PL310 errata: Clean & Invalidate maintenance operations do not invalidate clean lines"
922 Invalidate maintenance operations: by Physical Address
928 as clean lines are not invalidated as a result of these operations.
|
| D | proc-sa1100.S | 45 mcr p15, 0, r0, c9, c0, 5 @ Allow read-buffer operations from userland
|
| /linux-4.4.14/Documentation/w1/ |
| D | w1.generic | 31 almost any kind of operations. Each logical operation is a transaction
32 in nature, which can contain several (two or one) low-level operations.
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | powersave.txt | 22 operations.
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/ |
| D | pd-samsung.txt | 28 domain on/off operations.
|
| /linux-4.4.14/drivers/video/fbdev/omap/ |
| D | Kconfig | 56 (SDRAM) this will speed up graphics DMA operations.
|
| /linux-4.4.14/crypto/asymmetric_keys/ |
| D | Kconfig | 6 the asymmetric keys used for public key cryptographic operations such
|
| /linux-4.4.14/drivers/infiniband/ |
| D | Kconfig | 32 hardware for fast-path operations. You will also need
|
| /linux-4.4.14/drivers/cpuidle/ |
| D | Kconfig.arm | 11 initialized by calling the CPU operations init idle hook
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | head64.S | 67 .quad .Llinkage_stack # cr15: linkage stack operations
|
| /linux-4.4.14/net/can/ |
| D | Kconfig | 51 They can be modified with AND/OR/XOR/SET operations as configured
|
| /linux-4.4.14/Documentation/zh_CN/arm/ |
| D | kernel_user_helpers.txt | 78 fprintf(stderr, "can't do atomic operations, kernel too old\n");
|
| /linux-4.4.14/Documentation/netlabel/ |
| D | lsm_interface.txt | 32 level functions are translated into low level protocol operations based on how
|
| /linux-4.4.14/Documentation/usb/ |
| D | anchors.txt | 23 freed with normal memory management operations.
|
| D | chipidea.txt | 15 1.2 Test operations
|
| /linux-4.4.14/Documentation/fb/ |
| D | tgafb.txt | 58 me, however this server does not do acceleration, which make certain operations
|
| /linux-4.4.14/drivers/mtd/onenand/ |
| D | Kconfig | 49 operations as any other NAND Flash Array memory block.
|
| /linux-4.4.14/Documentation/trace/ |
| D | coresight.txt | 167 perform base operations related to the components, each component having
184 Specific class of device (source, link, or sink) have generic operations
186 "**groups" is a list of sysfs entries pertaining to operations
|
| /linux-4.4.14/Documentation/timers/ |
| D | NO_HZ.txt | 84 number of expensive clock-reprogramming operations.
324 operations (such as kernel module unload operations) that
342 o Some process-handling operations still require the occasional
343 scheduling-clock tick. These operations include calculating CPU
|
| D | hrtimers.txt | 127 representation of ktime_t values and operations is implemented via
133 on 32bit CPUs. Such operations are frequently necessary to convert
|
| /linux-4.4.14/Documentation/vm/ |
| D | cleancache.txt | 69 cleancache invalidate operations as required.
145 coherency (via cleancache_invalidate operations) between cleancache,
223 file removal or truncation operations either go through VFS or
224 add hooks to do the equivalent cleancache "invalidate" operations
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | marvell,berlin.txt | 41 CPU control register allows various operations on CPUs, like resetting them
|
| D | psci.txt | 6 operations.
|
| D | l2cc.txt | 23 maintenance operations on L1 are broadcasted to the L2 and L2
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-log.txt | 14 implementations use to perform logging operations (see
|
| /linux-4.4.14/Documentation/security/ |
| D | keys-ecryptfs.txt | 12 operations.
|
| D | credentials.txt | 196 credentials are manipulated and inherited over certain operations such as
224 operations that a task may do. Currently Linux supports several LSM
228 rules (policies) that say what operations a task with one label may do to
240 recorded in the file struct created. This allows operations using that file
268 operations allowed or disallowed as a result. In the case of execve(), the
|
| /linux-4.4.14/Documentation/filesystems/configfs/ |
| D | configfs.txt | 111 collection of items that share the same attributes and operations.
113 handles that. The group has a set of operations to perform these tasks
177 operations can be performed on a config_item. All items that have been
226 accomplished via the group operations specified on the group's
447 configfs still uses only normal filesystem operations. An item is
|
| /linux-4.4.14/Documentation/mic/ |
| D | mic_overview.txt | 8 host driver supports OSPM suspend and resume operations. It shuts down
|
| /linux-4.4.14/Documentation/mmc/ |
| D | mmc-dev-attrs.txt | 37 to trim or secure trim operations where the minimum size is
|
| /linux-4.4.14/drivers/net/ethernet/qlogic/ |
| D | Kconfig | 53 get operations support through rtNetlink interface. Only CEE
|
| /linux-4.4.14/drivers/staging/lustre/ |
| D | sysfs-fs-lustre | 235 Limit Lustre vfs operations gathering to just a single pid.
242 Limit Lustre vfs operations gathering to just a single ppid.
249 Limit Lustre vfs operations gathering to just a single gid.
350 cancelled by verious operations and bundle the cancellation
537 When a file is considered contended, all operations switch to
|
| /linux-4.4.14/Documentation/wimax/ |
| D | README.wimax | 21 stack will call in order to implement control operations requested by
|
| /linux-4.4.14/lib/raid6/ |
| D | int.uc | 52 * These sub-operations are separate inlines since they can sometimes be
|
| /linux-4.4.14/arch/frv/ |
| D | Kconfig | 73 bool "Out-of-line the FRV atomic operations"
76 Setting this option causes the FR-V atomic operations to be mostly
|
| /linux-4.4.14/Documentation/blockdev/ |
| D | zram.txt | 63 thus allowing up to max_comp_streams concurrent compression operations.
170 max_comp_streams RW the number of possible concurrent compress operations
|
| D | floppy.txt | 63 certain controllers. This may speed up certain operations.
187 Print informational messages for some operations (disk change
|
| /linux-4.4.14/arch/m68k/ifpsp060/src/ |
| D | pfpsp.S | 1279 # bit five of the fp extension word separates the monadic and dyadic operations
2401 # This exception handles 3 types of operations: #
2407 # For immediate data operations, the data is read in w/ a #
2608 # SNAN : all operations
2609 # OPERR : all reg-reg or mem-reg operations that can normally operr
2614 # INEX1 : all packed immediate operations
3327 # this would be the case for opclass two operations with a source infinity or
3350 # byte, word, long, and packed destination format operations can pass
3351 # through here. since packed format operations already were handled by
3790 # this would be the case for opclass two operations with a source zero
[all …]
|
| /linux-4.4.14/drivers/scsi/mpt3sas/ |
| D | Kconfig | 27 # programs or equipment, and unavailability or interruption of operations.
|
| /linux-4.4.14/drivers/scsi/ufs/ |
| D | Kconfig | 30 # and unavailability or interruption of operations. Under no
|
| /linux-4.4.14/arch/arm/crypto/ |
| D | Kconfig | 81 demonstrates excellent performance. Rijndael's operations are
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | pids.txt | 22 Organisational operations are not blocked by cgroup policies, so it is possible
|
| /linux-4.4.14/Documentation/fmc/ |
| D | carrier.txt | 66 * op: the operations to act on the device.
193 operations. The interrupt number is listed in the device
306 Given the typical use case of FMC devices, GPIO operations are not
|
| /linux-4.4.14/arch/arm/common/ |
| D | mcpm_head.S | 130 @ Wait for any previously-pending cluster teardown operations to abort
|
| /linux-4.4.14/Documentation/x86/ |
| D | tlb.txt | 51 determine how long the flush operations are taking.
|
| /linux-4.4.14/Documentation/s390/ |
| D | monreader.txt | 116 File operations:
118 The following file operations are supported: open, release, read, poll.
|
| /linux-4.4.14/drivers/dma/ |
| D | Kconfig | 12 RAID operations in the MD driver. This menu only presents
545 memcpy, memset, xor, and raid6 p+q operations. If your platform has
546 a dma engine that can perform raid operations and you have enabled
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig.cpu | 204 operations.
322 memory operations to violate the x86 ordering standard in rare cases.
325 memory barrier operations.
|
| /linux-4.4.14/Documentation/cdrom/ |
| D | cdrom-standard.tex | 157 of common {\em \cdrom\ device operations}, $<cdrom-device>_dops$.
158 These operations are different from the classical block-device file
159 operations, $<block-device>_fops$.
221 The device operations structure, $cdrom_device_ops$, contains a list
284 & struct\ cdrom_device_ops *& ops;& device operations for this major\cr
300 built, using the $next$ field. The device number, the device operations
760 with the kernel, the device operations and information structures,
813 operations, ones that are routed through the call $audio_ioctl()$, and
821 calling device-operations in $cdrom_device_ops$, if implemented and
965 \item Copy an example of the device-operations $struct$ to your
|
| /linux-4.4.14/Documentation/mtd/nand/ |
| D | pxa3xx-nand.txt | 12 larger pages, I/O operations on 4 KiB and 8 KiB pages is done with a set of
|