| /linux-4.1.27/Documentation/DocBook/ |
| D | .kernel-locking.xml.cmd | 1 …cBook/kernel-locking.xml := SRCTREE=./ ./scripts/docproc doc Documentation/DocBook/kernel-locking.…
2 Documentation/DocBook/kernel-locking.xml: Documentation/DocBook/kernel-locking.tmpl include/linux/m…
|
| D | Makefile | 10 kernel-hacking.xml kernel-locking.xml deviceiobook.xml \
|
| /linux-4.1.27/Documentation/filesystems/ |
| D | mandatory-locking.txt | 8 0. Why you should avoid mandatory locking
27 1. What is mandatory locking?
30 Mandatory locking is kernel enforced file locking, as opposed to the more usual
31 cooperative file locking used to guarantee sequential access to files among
42 "advisory" locking scheme. However, the world isn't perfect, and there's
46 with a "mandatory" locking scheme, whereby the operating system kernel would
51 The System V mandatory locking scheme was intended to have as little impact as
53 as candidates for mandatory locking, and using the existing fcntl()/lockf()
57 the whole truth. System V locking is based on fcntl(). The granularity of
58 fcntl() is such that it allows the locking of byte ranges in files, in addition
[all …]
|
| D | 00-INDEX | 4 - info on locking rules as they pertain to Linux VFS.
44 directory-locking
45 - info about the locking scheme used for directory operations.
73 - info on the Global File System 2 - Glock internal locking rules.
91 - info on file locking implementations, flock() vs. fcntl(), etc.
94 mandatory-locking.txt
95 - info on the Linux implementation of Sys V mandatory file locking.
109 - info on path walking and name lookup locking.
|
| D | locks.txt | 56 Mandatory locking, as described in
57 'Documentation/filesystems/mandatory-locking.txt' was prior to this release a
63 From this release of the kernel, mandatory locking can be turned on and off
65 The default is to disallow mandatory locking. The intention is that
66 mandatory locking only be enabled on a local filesystem as the specific need
|
| D | Locking | 1 The text below describes the locking rules for VFS-related methods.
3 prototypes or locking protocols - update this file. And update the relevant
24 locking rules:
72 locking rules:
107 See Documentation/filesystems/directory-locking for more detailed discussion
108 of the locking scheme for directory operations.
130 locking rules:
160 writes to quota files with quotas on). For other details about locking
170 locking rules:
207 locking rules:
[all …]
|
| D | dlmfs.txt | 36 dlmfs for easy to setup and easy to use clustered locking in
64 system calls and presents a more traditional locking api.
69 locking.
130 For more information on the VMS distributed locking API.
|
| D | gfs2.txt | 14 GFS uses interchangeable inter-node locking mechanisms, the currently
19 lock_dlm -- uses a distributed lock manager (dlm) for inter-node locking
|
| D | files.txt | 4 This document describes how locking for files (struct file)
19 the reference counting is similar, but the locking is
33 appear atomic. Here are the locking rules for
|
| D | porting | 72 change your internal locking. Otherwise exclusion warranties remain the
80 it by internal locking (most of filesystems couldn't care less) - you
81 can relax your locking.
89 - that will guarantee the same locking you used to have. If your method or its
222 Audit your code and add locking if needed. Notice that any place that is
245 return - that will guarantee the same locking you used to have. If
332 .d_compare() calling convention and locking rules are significantly
339 .d_hash() calling convention and locking rules are significantly
425 anymore, so if you require i_mutex locking you must make sure to take it and
|
| D | gfs2-glocks.txt | 1 Glock internal locking rules
78 if possible, in order to try and speed up the fast path though the locking.
80 such that any local locking will be done with the i_mutex as required
101 Glock locking order within GFS2:
113 itself (locking order as above), and the other, known as the iopen
|
| D | directory-locking | 102 But locking rules for cross-directory rename guarantee that we do not
118 While this locking scheme works for arbitrary DAGs, it relies on
|
| D | path-lookup.txt | 1 Path walking and name lookup locking
22 Since 2.5.62 kernel, dcache has been using a new locking model that uses RCU to
375 Papers and other documentation on dcache locking
380 2. http://lse.sourceforge.net/locking/dcache/dcache.html
|
| D | dax.txt | 66 - ensuring that there is sufficient locking between reads, writes,
|
| D | relay.txt | 288 they use the proper locking for such a buffer, either by wrapping
290 creating a local version that internally does the proper locking.
|
| D | squashfs.txt | 258 units this may introduce additional complexity in terms of locking and
|
| D | vfs.txt | 24 on are called from a process context. Filesystem locking is described
279 freeze_fs: called when VFS is locking a filesystem and
770 do not set those flags due to locking problems (jbd). This callback
974 Same locking and synchronisation rules as d_compare regarding
|
| D | fuse.txt | 279 whole system. For example a suid application locking a
|
| D | hpfs.txt | 223 Rewritten locking to avoid race-conditions
|
| D | ext4.txt | 364 dioread_nolock locking. If the dioread_nolock option is specified
|
| D | xfs-delayed-logging-design.txt | 164 is not changing while we do this. This requires locking the object to prevent
|
| /linux-4.1.27/Documentation/locking/ |
| D | lockdep-design.txt | 1 Runtime locking correctness validator
13 respect to locking rules, even if the locks may have multiple (possibly
37 Where STATE can be either one of (kernel/locking/lockdep_states.h)
44 When locking rules are violated, these state bits are presented in the
45 locking error messages, inside curlies. A contrived example:
91 other locking sequence between the acquire-lock operations, the
106 The above rules are enforced for any locking sequence that occurs in the
130 Exception: Nested data dependencies leading to nested locking
140 An example of such an object hierarchy that results in "nested locking"
145 automatically detect this natural ordering, as the locking rule behind
[all …]
|
| D | mutex-design.txt | 9 In the Linux kernel, mutexes refer to a particular locking primitive
24 and implemented in kernel/locking/mutex.c. These locks use a three
43 locking fastpath is 2 instructions:
94 - Recursive locking/unlocking is not permitted.
157 locking primitive.
|
| D | locktorture.txt | 6 that runs torture tests on core kernel locking primitives. The kernel
63 ** Torture-framework (RCU + locking) **
124 -only- be positive if there is a bug in the locking primitive's
145 were no locking failures, CPU-hotplug problems were detected.
|
| D | 00-INDEX | 4 - documentation on the runtime locking correctness validator.
|
| D | rt-mutex.txt | 41 locking overhead when locking an uncontended mutex or unlocking a mutex
|
| D | lglock.txt | 6 Location: kernel/locking/lglock.c
99 From the locking semantics it is a spinlock. It could be called a
|
| D | spinlocks.txt | 3 The most basic primitive for locking is spinlock.
39 to do locking across CPU's, which implies that EVERYTHING that
|
| D | ww-mutex-design.txt | 29 from a global counter. In case of deadlock while locking all the buffers
215 locking down the nodes those edges connect to.
233 when the dynamic locking step hits -EDEADLK we also need to unlock all the
|
| D | rt-mutex-design.txt | 230 locking the pi_lock, interrupts must be disabled.
240 The following shows a locking order of L1->L2->L3, but may not actually
286 in func4 in the "do something again" area, we have a locking that follows:
298 functions individually, it seems as though they only have at most a locking
299 depth of two. So, although the locking depth is defined at compile time,
458 is taken. This is done by a spin_trylock, because the locking order of the
729 mutex. This synchronizes the locking and unlocking of the mutex.
|
| /linux-4.1.27/fs/gfs2/ |
| D | Kconfig | 19 the locking module below. Documentation and utilities for GFS2 can
26 bool "GFS2 DLM locking"
30 Multiple node locking module for GFS2
32 Most users of GFS2 will require this. It provides the locking
|
| /linux-4.1.27/net/ax25/ |
| D | TODO | 15 Implement proper socket locking in netrom and rose.
17 Check socket locking when ax25_rcv is sending to raw sockets. In particular
|
| /linux-4.1.27/Documentation/ |
| D | percpu-rw-semaphore.txt | 5 optimized for locking for reading.
13 instruction in the lock and unlock path. On the other hand, locking for
|
| D | preempt-locking.txt | 10 A preemptible kernel creates new locking issues. The issues are the same as
12 kernel model leverages existing SMP locking mechanisms. Thus, the kernel
13 requires explicit additional locking for very few additional situations.
29 First, since the data is per-CPU, it may not have explicit SMP locking, but
123 in doubt, rely on locking or explicit preemption disabling.
|
| D | volatile-considered-harmful.txt | 32 If all the code follows the locking rules, the value of shared_data cannot
42 If shared_data were declared volatile, the locking would still be
46 volatile. When dealing with shared data, proper locking makes volatile
84 locking. So jiffies can be volatile, but the addition of other
|
| D | pi-futex.txt | 17 recursive locking, etc.
25 improve the statistical distribution of locking related application
53 to think about how to offer the option of a deterministic locking
61 problems as other user-space locking constructs). Fact is, pretty much
|
| D | robust-futex-ABI.txt | 21 mechanism, which handles uncontested locking without needing a system
22 call, and handles contested locking by maintaining a list of waiting
69 in the middle of a locking or unlocking operation.
101 larger, user level locking structures, one per lock. The kernel
114 Actual locking and unlocking, during normal operations, is handled
|
| D | irqflags-tracing.txt | 14 are locking APIs that are not used in IRQ context. (the one exception
|
| D | 00-INDEX | 288 locking/
289 - directory with info about kernel locking primitives
355 - RCU based read-write semaphore optimized for locking for reading
370 preempt-locking.txt
371 - info on locking under a preemptive kernel.
|
| D | SM501.txt | 16 include locking for common registers, clock control and resource
|
| D | vgaarbiter.txt | 130 be used. Then, the card is marked as locking these resources and the IO and/or
133 if some conflicting card is already locking one of the required resources (or
|
| D | kref.txt | 118 know what you are doing (there are some situations where locking is
257 locking for lookups in the above example:
|
| D | iostats.txt | 98 but due to the lack of locking it may only be very close.
100 In 2.6, there are counters for each CPU, which make the lack of locking
|
| D | sparse.txt | 57 locking. These annotations tell sparse when a lock is held, with
|
| D | clk.txt | 281 This effectively divides operations in two groups from a locking perspective.
297 Note that locking must also be considered when code outside of the common
|
| D | robust-futexes.txt | 58 - it has quite complex locking and race scenarios. The vma-based
141 - the implementation and the locking is "obvious", and there are no
|
| D | pwm.txt | 113 PWM core does not enforce any locking to pwm_enable(), pwm_disable() and
|
| D | DMA-ISA-LPC.txt | 96 (and everyone else) uses the locking functions then you only need to
|
| D | flexible-arrays.txt | 26 locking at all; if concurrent access to an array is possible, then the
|
| D | kernel-docs.txt | 305 Keywords: HOWTO, kernel contexts, deadlock, locking, modules,
354 Location: in kernel tree, Documentation/DocBook/kernel-locking.tmpl
356 Keywords: locks, locking, spinlock, semaphore, atomic, race
359 locking system in the Linux Kernel either in uniprocessor or SMP
|
| D | memory-barriers.txt | 39 (*) Inter-CPU locking barrier effects.
1652 references to shared memory on SMP systems, though the use of locking instead
1758 which are locking and scheduling functions.
1768 The Linux kernel has a number of locking constructs:
1812 Certain locking variants of the ACQUIRE operation may fail, either due to
1884 a sleep-unlock race, but the locking primitive needs to resolve
1915 See also the section on "Inter-CPU locking barrier effects".
2106 On SMP systems locking primitives give a more substantial form of barrier: one
2436 The following operations are special locking primitives:
2443 preference to other operations when implementing locking primitives, because
[all …]
|
| D | rtc.txt | 63 built in locking so that only one process is allowed to have the /dev/rtc
|
| D | rbtree.txt | 169 modified or wrapped (except for locking purposes):
|
| D | cpu-hotplug.txt | 97 no locking rules as of now. Typical usage is to init topology during boot,
|
| D | CodingStyle | 591 Reference counting means that you can avoid locking, and allows multiple
596 Note that locking is _not_ a replacement for reference counting.
|
| D | vfio.txt | 95 for disabling driver probing/locking a device.
|
| D | assoc_array.txt | 564 this without locking against a read - so we have to replace that node too.
|
| D | kobject.txt | 140 kobject_rename does not perform any locking or have a solid notion of
|
| D | atomic_ops.txt | 524 locking scheme is being used to protect the bitmask, and thus less
|
| D | kernel-parameters.txt | 811 Print debugging info while doing the locking API
1824 Set the number of locking read-acquisition kthreads.
1829 Set the number of locking write-acquisition kthreads.
1854 This tests the locking primitive's ability to
1861 Specify the locking implementation to test.
|
| D | HOWTO | 159 locking properly. The documents will be created in the
|
| D | devices.txt | 3310 be the PID of the locking process as an ASCII number.
3313 which point to serial ports. In order to ensure proper locking in the
|
| /linux-4.1.27/drivers/thermal/ti-soc-thermal/ |
| D | TODO | 7 - Revisit need for locking
|
| /linux-4.1.27/Documentation/serial/ |
| D | 00-INDEX | 16 - guide to the locking policies of the tty layer.
|
| D | tty.txt | 4 Your guide to the ancient and twisted locking policies of the tty layer and
253 shouldn't try and do clever locking here.
|
| D | driver | 41 necessary locking using port->lock. There are some exceptions (which
56 locking.
|
| /linux-4.1.27/drivers/md/persistent-data/ |
| D | Kconfig | 16 block manager locking used by thin provisioning and caching.
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | 00-INDEX | 11 locking.txt
|
| D | mmu.txt | 292 the description in Documentation/virtual/kvm/locking.txt.
|
| /linux-4.1.27/fs/ncpfs/ |
| D | Kconfig | 34 bool "Proprietary file locking"
37 Allows locking of records on remote volumes. Say N unless you have
38 special applications which are able to utilize this locking scheme.
|
| /linux-4.1.27/drivers/staging/lustre/ |
| D | README.txt | 39 Disable posix file locking (Applications trying to use
48 Enable cluster-global posix file locking coherent across all
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-ocfs2 | 13 of ocfs2 locking supported by the filesystem. This version
14 covers how ocfs2 uses distributed locking between cluster
|
| /linux-4.1.27/fs/btrfs/ |
| D | Makefile | 8 extent_io.o volumes.o async-thread.o ioctl.o locking.o orphan.o \
|
| /linux-4.1.27/drivers/gpu/vga/ |
| D | Kconfig | 17 Reserves space in the kernel to maintain resource locking for
|
| /linux-4.1.27/Documentation/RCU/ |
| D | UP.txt | 76 If call_rcu() directly invokes the callback, painful locking restrictions
79 Quick Quiz #2: What locking restriction must RCU callbacks respect?
107 What locking restriction must RCU callbacks respect?
|
| D | whatisRCU.txt | 278 locking.
428 need to use locking (or something similar) to keep concurrent
541 in terms of familiar locking primitives, and another that more closely
557 familiar locking primitives. Its overhead makes it a non-starter for
679 RCU is analogous to reader-writer locking. The following unified
680 diff shows how closely related RCU and reader-writer locking can be.
771 Either way, the differences are quite small. Read-side locking moves
772 to rcu_read_lock() and rcu_read_unlock, update-side locking moves from
|
| D | checklist.txt | 6 result in the same sorts of problems that leaving out a locking primitive
31 a. locking,
346 an issue, the memory-allocator locking handles it). However,
348 must use whatever locking or other synchronization is required
|
| D | listRCU.txt | 13 The best applications are cases where, if reader-writer locking were
142 audit_netlink_sem, so no additional locking is required. The auditsc_lock
|
| D | RTFP.txt | 48 providing a fine-grained locking design, however, it would be interesting
89 but reduces memory latency, contention, and locking overheads.
100 greatly simplifies locking hierarchies and helps avoid deadlocks.
114 in 2004 [MagedMichael04a]. This technique eliminates locking, reduces
144 [McKenney04a], a performance comparison of locking to RCU on several
255 concept of read-copy locking.
288 concept of read-copy locking.
614 \url{http://lse.sourceforge.net/locking/rcu/rcupdate_doc.html}
987 Compares performance of RCU to that of other locking primitives
1602 the semantics of reader-writer locking. This is a recursive
[all …]
|
| D | rcubarrier.txt | 6 of as a replacement for read-writer locking (among other things), but with
|
| D | rcu_dereference.txt | 265 Then one approach is to use locking, for example, as follows:
|
| /linux-4.1.27/Documentation/networking/ |
| D | netdev-features.txt | 134 NETIF_F_LLTX should be set in drivers that implement their own locking in
135 transmit path or don't need locking at all (e.g. software tunnels).
137 NETDEV_TX_LOCKED when the spin lock fails. The locking should also properly
|
| D | netdevices.txt | 74 The locking there should also properly protect against
|
| D | fib_trie.txt | 111 However, the functions are somewhat separated for other possible locking
|
| D | vortex.txt | 252 Later (current) versions of the driver _do_ support locking of the
|
| D | ppp_generic.txt | 199 are required to provide the appropriate locking on the ppp_channel
|
| /linux-4.1.27/drivers/staging/slicoss/ |
| D | TODO | 30 - locking too fine grained, not designed just throw more locks
|
| /linux-4.1.27/Documentation/mmc/ |
| D | mmc-dev-parts.txt | 35 not support boot partition locking, the file will not exist. If the
|
| /linux-4.1.27/Documentation/filesystems/pohmelfs/ |
| D | design_notes.txt | 14 locking messages.
53 given inode, which is guarded by an appropriate locking protocol.
|
| /linux-4.1.27/Documentation/ide/ |
| D | ChangeLog.ide-cd.1994-2004 | 45 * Add door locking.
132 * to fix the drive door locking problems.
143 * Better detection if door locking isn't supported
246 * - Fix locking mania and make ide_cdrom_reset relock
|
| D | ChangeLog.ide-tape.1995-2002 | 52 * ide.c. The hwgroup locking method which was used
|
| /linux-4.1.27/Documentation/development-process/ |
| D | 4.Coding | 153 (now called mac80211) could be merged, a locking scheme needed to be
161 code could be written without thinking about locking are long past.
166 locking after the fact is a rather more difficult task. Kernel developers
167 should take the time to understand the available locking primitives well
248 number of common locking errors.
255 One of the heavier debugging tools is the locking checker, or "lockdep."
265 locking should be run with lockdep enabled before being submitted for
360 locking rules for data structures generally need to be explained somewhere.
|
| D | 7.AdvancedTopics | 161 locking here is wrong."
167 will check for problematic locking, excessive stack usage, possible
|
| D | 3.Early-stage | 100 locking and such into code is a difficult task; as a result, the merging
|
| /linux-4.1.27/Documentation/pcmcia/ |
| D | locking.txt | 1 This file explains the locking and exclusion scheme used in the PCCARD
|
| /linux-4.1.27/drivers/sh/maple/ |
| D | maple.c | 448 int x, locking; in maple_vblank_handler() local
477 locking = maple_add_packet(mdev, 0, in maple_vblank_handler()
479 if (!locking) in maple_vblank_handler()
|
| /linux-4.1.27/fs/affs/ |
| D | Changes | 51 - locking fixes
66 - locking fixes for link creation/removal.
80 - locking should be safe for the future
|
| /linux-4.1.27/drivers/mtd/maps/ |
| D | vmu-flash.c | 234 int partition, error, locking, x, phaselen, wait; in maple_vmu_write_block() local
267 locking = maple_add_packet(mdev, MAPLE_FUNC_MEMCARD, in maple_vmu_write_block()
271 if (locking) { in maple_vmu_write_block()
|
| /linux-4.1.27/drivers/staging/i2o/ |
| D | README | 25 Fixed assorted dumb SMP locking bugs
|
| /linux-4.1.27/Documentation/timers/ |
| D | timer_stats.txt | 8 locking is per-CPU and lookup is hashed.
|
| D | hrtimers.txt | 107 CLOCK_REALTIME timers along with complex locking. In case of
116 The locking and per-CPU behavior of hrtimers was mostly taken from the
|
| /linux-4.1.27/arch/mips/cavium-octeon/ |
| D | Kconfig | 41 Enable locking parts of the kernel into the L2 cache.
|
| /linux-4.1.27/Documentation/scheduler/ |
| D | sched-arch.txt | 7 1. Runqueue locking
|
| /linux-4.1.27/fs/ |
| D | Kconfig | 66 bool "Enable POSIX file locking API" if EXPERT
69 This option enables standard file locking support, required
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 969 bool "Lock debugging: prove locking correctness"
978 This feature enables the kernel to prove that all locking
981 not yet triggered) combination of observed locking
986 In short, this feature enables the kernel to report locking
999 If a deadlock is impossible (i.e. the locking rules, as
1005 different locking variants are observed and mapped too, and
1007 arbitrary combination of these separate locking variants.
1009 For more details, see Documentation/locking/lockdep-design.txt.
1030 For more details, see Documentation/locking/lockstat.txt
1063 bootup. The self-test checks whether common types of locking bugs
[all …]
|
| D | Makefile | 52 obj-$(CONFIG_DEBUG_LOCKING_API_SELFTESTS) += locking-selftest.o
|
| /linux-4.1.27/Documentation/devicetree/bindings/mtd/ |
| D | mtd-physmap.txt | 31 Bits) locking.
|
| /linux-4.1.27/fs/jffs2/ |
| D | README.Locking | 5 This document attempts to describe the existing locking rules for
112 will not be removed. So, it is allowed to access it without locking
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | persistent-data.txt | 33 is a read/write locking interface to prevent concurrent accesses, and
|
| /linux-4.1.27/Documentation/ptp/ |
| D | ptp.txt | 68 against concurrent access. This locking cannot be accomplished in
|
| /linux-4.1.27/Documentation/x86/x86_64/ |
| D | machinecheck | 53 normal kernel locking rules. The tolerance level configures
|
| /linux-4.1.27/kernel/ |
| D | Makefile | 26 obj-y += locking/
|
| /linux-4.1.27/Documentation/infiniband/ |
| D | core_locking.txt | 3 This guide is an attempt to make explicit the locking assumptions
|
| /linux-4.1.27/Documentation/filesystems/nfs/ |
| D | rpc-server-gss.txt | 88 locking into the legacy mechanisms, the above steps must be performed
|
| D | rpc-cache.txt | 24 - general cache lookup with correct locking
|
| /linux-4.1.27/Documentation/security/ |
| D | credentials.txt | 335 to read or replace its own credentials without the need for any form of locking
388 Whilst a task may access its own credentials without the need for locking, the
459 locking to alter its own credentials.
563 It is safe to access f_cred without the use of RCU or locking because the
|
| D | keys.txt | 1053 there's no need to indulge in RCU or locking when accessing the payload.
1062 be accessed without any form of locking, provided that it's known to be
1326 prevent the key's payload changing. It is not necessary to use RCU locking
|
| /linux-4.1.27/Documentation/power/ |
| D | pm_qos_interface.txt | 34 reading the aggregated value does not require any locking mechanism.
105 the aggregated value does not require any locking mechanism.
|
| D | opp.txt | 82 WARNING on OPP List locking mechanism:
94 RCU locking mechanisms. These functions should *NOT* be called under RCU locks
|
| D | suspend-and-cpuhotplug.txt | 13 the locking involved. It outlines the notifications involved as well.
|
| /linux-4.1.27/drivers/clocksource/ |
| D | Kconfig | 123 locking implementations. It might also be useful for imposing timeout
|
| /linux-4.1.27/Documentation/usb/ |
| D | callbacks.txt | 46 All callbacks are mutually exclusive. There's no need for locking
|
| /linux-4.1.27/drivers/gpu/drm/ |
| D | Kconfig | 127 # !PREEMPT because of missing ioctl locking
|
| /linux-4.1.27/Documentation/vm/ |
| D | hwpoison.txt | 26 * has to be extremely careful. Generally it tries to use normal locking
|
| D | numa_memory_policy.txt | 360 or by prefaulting the entire shared memory region into memory and locking
|
| D | unevictable-lru.txt | 441 sections above. Both processes (migration and m[un]locking) hold the page
|
| /linux-4.1.27/Documentation/scsi/ |
| D | scsi_eh.txt | 181 1. Checks if door locking is needed and locks door.
279 LOCKING: queue or finish function performs appropriate locking
|
| D | libsas.txt | 64 The idea is to avoid unnecessary locking.
|
| D | aic7xxx.txt | 162 - Fix locking regression introduced in 6.2.29 that
|
| D | aic79xx.txt | 142 - Simplify driver locking by releasing the io_request_lock
|
| D | st.txt | 374 MT_ST_AUTO_LOCK automatic locking of the drive door (global)
|
| D | ChangeLog.lpfc | 225 * Fix double locking bug in the error handling part of
1308 * Several locking improvements.
|
| D | ChangeLog.1992-1997 | 1893 a removable device says ILLEGAL REQUEST to a door-locking command,
|
| /linux-4.1.27/drivers/md/ |
| D | Kconfig | 185 Clustering support for MD devices. This enables locking and
246 Some bio locking schemes used by other device-mapper targets
|
| /linux-4.1.27/drivers/mtd/chips/ |
| D | Kconfig | 151 This enables support for reading, writing and locking so called
|
| /linux-4.1.27/Documentation/block/ |
| D | biodoc.txt | 72 5.1 Granular locking: Removal of io_request_lock
1052 granular locking. The request queue structure has a pointer to the
1053 lock to be used for that queue. As a result, locking can now be
1056 corresponding adapter lock, which results in a per host locking
1057 granularity). The locking semantics are the same, i.e. locking is
|
| /linux-4.1.27/Documentation/filesystems/caching/ |
| D | object.txt | 148 state machine at once, this simplifies the locking, particularly with respect
|
| /linux-4.1.27/Documentation/cpu-freq/ |
| D | governors.txt | 246 CPUfreq core to ensure proper locking.
|
| /linux-4.1.27/Documentation/filesystems/cifs/ |
| D | CHANGES | 242 on requests on other threads. Improve POSIX locking emulation,
263 POSIX locking to servers which support CIFS POSIX Extensions
289 locking support (requires server with newest CIFS UNIX Extensions
660 Fix byte range locking bug (endian problem) causing bad offset and
|
| D | README | 2 features such as hierarchical dfs like namespace, hardlinks, locking and more.
505 locking, send only mandatory lock requests. For some
508 locking, they may be able to take advantage of this option,
|
| /linux-4.1.27/Documentation/video4linux/ |
| D | v4l2-framework.txt | 648 - lock: leave to NULL if you want to do all the locking in the driver.
711 ioctls and locking
714 The V4L core provides optional locking services. The main service is the
729 Of course, you can always do all the locking yourself by leaving both lock
|
| /linux-4.1.27/Documentation/watchdog/ |
| D | watchdog-kernel-api.txt | 106 If the watchdog_device struct is dynamically allocated, just locking the module
|
| /linux-4.1.27/Documentation/x86/ |
| D | intel_mpx.txt | 156 if mmap() would work it still requires locking or nasty tricks to
|
| /linux-4.1.27/Documentation/arm/OMAP/ |
| D | DSS | 351 DSS locking
|
| /linux-4.1.27/fs/befs/ |
| D | ChangeLog | 396 * Removed superblock locking calls in befs_read_super(). In 2.4, the VFS
|
| /linux-4.1.27/arch/ |
| D | Kconfig | 437 locking is needed to protect against concurrent accesses.
|
| /linux-4.1.27/Documentation/arm/ |
| D | cluster-pm-race-avoidance.txt | 31 Simple locking may not be sufficient to solve this problem, because
|
| /linux-4.1.27/Documentation/cdrom/ |
| D | cdrom-standard.tex | 412 This function (and no other code) controls locking of the door, if the
413 drive allows this. The value of $lock$ controls the desired locking
999 movement, door locking, etc.).
|
| /linux-4.1.27/mm/ |
| D | Kconfig | 304 # initiates buffer writeback without locking the page or setting PG_writeback,
|
| /linux-4.1.27/Documentation/cgroups/ |
| D | unified-hierarchy.txt | 441 details in a way which can exert significant pain by locking the
|
| /linux-4.1.27/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 506 and acquire the lock (see Documentation/DocBook/kernel-locking).
|
| D | pci.txt | 584 having sane locking.
|
| /linux-4.1.27/Documentation/isdn/ |
| D | README | 72 O N L Y !!! for debugging (no locking against other devices):
|
| /linux-4.1.27/ |
| D | MAINTAINERS | 6079 T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core/locking
6081 F: Documentation/locking/lockdep*.txt
6082 F: Documentation/locking/lockstat.txt
6084 F: kernel/locking/
7851 F: Documentation/preempt-locking.txt
|
| D | CREDITS | 1404 D: fixed keyboard driver to separate LED and locking status
|