/linux-4.4.14/drivers/staging/lustre/lustre/libcfs/linux/ |
D | linux-tracefile.c | 150 int cfs_trace_lock_tcd(struct cfs_trace_cpu_data *tcd, int walking) in cfs_trace_lock_tcd() argument 158 else if (unlikely(walking)) in cfs_trace_lock_tcd() 165 void cfs_trace_unlock_tcd(struct cfs_trace_cpu_data *tcd, int walking) in cfs_trace_unlock_tcd() argument 173 else if (unlikely(walking)) in cfs_trace_unlock_tcd()
|
/linux-4.4.14/Documentation/filesystems/ |
D | path-lookup.txt | 1 Path walking and name lookup locking 6 will be resolved. Paths are resolved by walking the namespace tree, starting 15 Path walking synchronisation history: 18 algorithm changed this by holding the dcache_lock at the beginning and walking 26 dentry that was looked up, so that may be used as the basis for walking the 37 path walking. 39 Path walking overview 60 name in the name string, and require some recursive path walking. Mount points 64 exact path walking flags. 66 Path walking then must, broadly, do several particular things: [all …]
|
D | 00-INDEX | 109 - info on path walking and name lookup locking.
|
D | porting | 364 vfs now tries to do path walking in "rcu-walk mode", which avoids
|
D | xfs-self-describing-metadata.txt | 15 other metadata structures need to be discovered by walking the filesystem
|
D | ext4.txt | 581 inode to ext4 extent mapped inode by walking
|
D | xfs-delayed-logging-design.txt | 641 flushing the CIL could involve walking a list of tens of thousands of log
|
D | vfs.txt | 1034 ordinary directory and returned to pathwalk to continue walking.
|
/linux-4.4.14/drivers/staging/lustre/lustre/libcfs/ |
D | tracefile.h | 260 int cfs_trace_lock_tcd(struct cfs_trace_cpu_data *tcd, int walking); 261 void cfs_trace_unlock_tcd(struct cfs_trace_cpu_data *tcd, int walking);
|
/linux-4.4.14/Documentation/ABI/testing/ |
D | sysfs-class-fpga-manager | 19 states. The fpga manager driver is walking through these steps
|
/linux-4.4.14/tools/perf/Documentation/ |
D | intel-bts.txt | 12 While decoding Intel BTS does not require walking the object code, the object
|
D | intel-pt.txt | 19 Trace data must be 'decoded' which involves walking the object code and matching
|
/linux-4.4.14/Documentation/fault-injection/ |
D | fault-injection.txt | 90 stacktrace walking. Failure is injected only if some caller
|
/linux-4.4.14/fs/jffs2/ |
D | README.Locking | 105 has to be locked while walking the c->inocache_list hash buckets.
|
/linux-4.4.14/Documentation/vm/ |
D | transhuge.txt | 314 Code walking pagetables but unware about huge pmds can simply call 323 If you're not walking pagetables but you run into a physical hugepage
|
D | unevictable-lru.txt | 262 replaced by walking the reverse map to determine whether any VM_LOCKED VMAs 529 try_to_unmap() checks for VM_LOCKED VMAs while it is walking a page's reverse
|
/linux-4.4.14/Documentation/scheduler/ |
D | sched-design-CFS.txt | 108 SMP load-balancing has been reworked/sanitized: the runqueue-walking
|
/linux-4.4.14/Documentation/ |
D | robust-futex-ABI.txt | 153 'list_op_pending' and the address of each 'lock word' found by walking
|
D | assoc_array.txt | 573 so as long as anyone doing walking or iteration holds the RCU read lock, the
|
D | DMA-API-HOWTO.txt | 124 walking page tables to get the physical addresses, and then
|
D | pinctrl.txt | 103 like this, walking around the edge of the chip, which seems to be industry
|
/linux-4.4.14/include/sound/ |
D | soc-dapm.h | 534 u32 walking:1; /* path is in the process of being walked */ member
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | mmu.txt | 404 For the large memory guests, walking and zapping all pages is really slow 428 invalidated. This also needs to hold the MMU lock while walking all
|
D | api.txt | 2809 > 0 if an exception occurred while walking the page tables 2831 access exception occurred while walking the MMU tables of the guest, the
|
/linux-4.4.14/sound/soc/ |
D | soc-dapm.c | 1102 if (path->walking) in is_connected_ep() 1108 path->walking = 1; in is_connected_ep() 1110 path->walking = 0; in is_connected_ep()
|
/linux-4.4.14/Documentation/locking/ |
D | ww-mutex-design.txt | 213 - They can handle lock-acquisition in any order which allows us to start walking
|
/linux-4.4.14/Documentation/hwmon/ |
D | w83781d | 379 suspected since walking through all the values increasingly and then
|
/linux-4.4.14/Documentation/filesystems/caching/ |
D | cachefiles.txt | 163 kernel module contains its own very cut-down path walking facility that ignores
|
/linux-4.4.14/mm/ |
D | Kconfig | 403 up the pagetable walking.
|
/linux-4.4.14/Documentation/scsi/ |
D | ChangeLog.ncr53c8xx | 453 of walking on the lun CCBs list. Up to 32 tags per lun are now
|
/linux-4.4.14/lib/ |
D | Kconfig.debug | 1153 walking routines. 1162 linked-list (plist) walking routines. This checks the entire
|
/linux-4.4.14/Documentation/networking/ |
D | can.txt | 480 while walking through the filter lists the CAN core provides an optimized
|