Searched refs:operations (Results 1 – 25 of 265) sorted by relevance
1234567891011
| /linux-2.6.39/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 …]
|
| /linux-2.6.39/Documentation/filesystems/ |
| D | xip.txt | 7 addition, read&write type file operations also transfer data from/to the page
18 completely. With execute-in-place, read&write type operations are performed
29 address space operation, and file operations.
49 do page cache read/write operations.
53 A set of file operations that do utilize get_xip_page can be found in
59 The generic file operations do_sync_read/do_sync_write can be used to implement
|
| 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:
81 Locking rules for glock operations:
105 4. Rgrp glock(s) (for (de)allocation operations)
106 5. Transaction glock (via gfs2_trans_begin) for non-read operations
|
| D | directory-locking | 1 Locking scheme used for directory operations is based on two
5 For our purposes all operations fall in 5 classes:
61 of operations).
78 It means that one of the operations is cross-directory rename.
94 These operations are guaranteed to avoid loop creation. Indeed,
108 also preserved by all operations (cross-directory rename on a tree that would
|
| 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 | 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
|
| /linux-2.6.39/Documentation/ |
| D | atomic_ops.txt | 24 The first operations to implement for atomic_t's are the initializers and
34 The initializer is atomic in that the return values of the atomic operations
52 The setting is atomic in that the return values of the atomic operations by
64 values initialized or modified with the interface operations if a proper
67 interface operations. atomic_read does not guarantee that the runtime
115 done such that all memory operations before and after the atomic
172 with the given old and new values. Like all atomic_xxx operations,
174 other accesses of *v are performed through atomic_xxx operations.
210 It makes sure that all memory operations preceding the atomic_dec()
221 ordering with respect to memory operations after an atomic_dec() call
[all …]
|
| D | local_ops.txt | 6 This document explains the purpose of the local atomic operations, how
13 * Purpose of local atomic operations
15 Local atomic operations are meant to provide fast and highly reentrant per CPU
16 counters. They minimize the performance cost of standard atomic operations by
25 Local atomic operations only guarantee variable modification atomicity wrt the
35 It can be done by slightly modifying the standard atomic operations : only
48 * Rules to follow when using local atomic operations
71 * How to use local atomic operations
84 operations : it makes sure that preemption is disabled around write access to
|
| 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:
210 the CPU will only issue the following sequence of memory operations:
266 As can be seen above, independent memory operations are effectively performed
272 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
|
| /linux-2.6.39/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-2.6.39/Documentation/ia64/ |
| D | paravirt_ops.txt | 23 It allows each hypervisor to override operations which are important for
27 operations corresponding to low level sensitive instructions and high
30 binary patch. It is because some of these operations are very
35 Thus, operations of paravirt_ops are classified into three categories.
37 These operations correspond to high level functionality so that the
41 Usually these operations correspond to low level instructions. They
98 This structure describes hooks to iosapic operations.
100 This structure describes hooks to irq related operations
|
| /linux-2.6.39/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
|
| /linux-2.6.39/net/rds/ |
| D | Kconfig | 15 This transport supports RDMA operations.
22 This transport does not support RDMA operations.
|
| /linux-2.6.39/tools/perf/Documentation/ |
| D | perf-bench.txt | 28 (executing 1000000 pipe operations between two tasks)
104 (executing 1000000 pipe operations between two tasks)
111 (executing 1000 pipe operations between two tasks)
|
| /linux-2.6.39/Documentation/filesystems/nfs/ |
| D | nfs41-server.txt | 27 Other NFSv4.1 features, Parallel NFS operations in particular,
33 does support ordinary file operations on clients we have tested against
60 - Mandatory operations which we do not support, such as
76 the operations that are mandatory to implement (REQ), optional
77 (OPT), and NFSv4.0 operations that are required not to implement (MNI)
78 in minor version 1. The first column indicates the operations that
87 I Implemented NFSv4.1 operations.
|
| /linux-2.6.39/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-2.6.39/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-2.6.39/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-2.6.39/Documentation/power/ |
| D | notifiers.txt | 4 There are some operations that device drivers may want to carry out in their
10 Also, there may be some operations, that subsystems want to carry out before a
47 operations performed for PM_SUSPEND_PREPARE should be reversed for
|
| /linux-2.6.39/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.
70 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-2.6.39/Documentation/networking/ |
| 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.
|
| /linux-2.6.39/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 a most of those operations.
|
| /linux-2.6.39/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:
|
1234567891011