Searched refs:callers (Results 1 – 25 of 32) sorted by relevance
12
| /Linux-v5.4/Documentation/vm/ |
| D | page_frags.rst | 28 allocation. The netdev_alloc_cache is used by callers making use of the
30 used by callers of the __napi_alloc_frag and __napi_alloc_skb calls. The
|
| D | unevictable-lru.rst | 490 The callers of populate_vma_page_range() will have already added the memory range
493 callers then subtract a non-negative return value from the task's locked_vm. A
|
| /Linux-v5.4/Documentation/networking/ |
| D | tc-actions-env-rules.txt | 17 The "environmental" rules for callers of actions (qdiscs etc) are:
|
| /Linux-v5.4/drivers/scsi/ |
| D | xen-scsifront.c | 126 unsigned callers; member
511 info->callers++; in scsifront_enter()
517 info->callers--; in scsifront_return()
518 if (info->callers) in scsifront_return()
912 while (info->callers && !err) { in scsifront_suspend()
|
| /Linux-v5.4/Documentation/media/uapi/dvb/ |
| D | dmx-fread.rst | 82 - The driver failed to write to the callers buffer due to an
|
| /Linux-v5.4/Documentation/process/ |
| D | deprecated.rst | 75 in callers. The respective :c:func:`kstrtol`, :c:func:`kstrtoll`,
95 buffer size, which may be a needless performance penalty for callers using
|
| D | 4.Coding.rst | 82 always passed as zero by all callers. One could retain that argument just
|
| /Linux-v5.4/Documentation/core-api/ |
| D | debug-objects.rst | 85 on the callers stack. If it is on the callers stack then a limited
108 the callers stack.
|
| D | timekeeping.rst | 73 more convenient for some callers.
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | porting.rst | 115 check for ->link() target not being a directory is done by callers. Feel
122 ->link() callers hold ->i_mutex on the object we are linking to. Some of your
312 nobh_write_begin, blockdev_direct_IO*) to callers. Take a look at
313 ext2_write_failed and callers for an example.
778 is returned and callers reference to inode is subsumed by that. On
|
| D | path-lookup.rst | 456 component remains for the caller to sort out. Those callers are
1175 For some callers, this is all they need; they want to create that
1177 callers will want to follow a symlink if one is found, and possibly
1179 than just the last component of the original file name. These callers
1341 Various callers set this and it is also set when the final component
|
| D | locking.rst | 366 keep it that way and don't breed new callers.
|
| D | relay.txt | 287 buffer - but since it is a global buffer, callers should make sure
|
| /Linux-v5.4/kernel/dma/ |
| D | Kconfig | 181 Perform extra checking that callers of dma_map_sg() have respected the
|
| /Linux-v5.4/Documentation/target/ |
| D | tcm_mod_builder.rst | 17 1) Generate new API callers for drivers/target/target_core_fabric_configs.c logic
|
| /Linux-v5.4/Documentation/trace/ |
| D | events-kmem.rst | 66 callers should be batching their activities.
|
| /Linux-v5.4/Documentation/driver-api/usb/ |
| D | dma.rst | 83 This may force your callers to do some bounce buffering, copying from
|
| /Linux-v5.4/drivers/block/paride/ |
| D | Transition-notes | 128 can be taken to callers as long as they remain within the area.
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-top.txt | 193 This has the effect of collecting the callers of each such
|
| D | perf-report.txt | 284 This has the effect of collecting the callers of each such
|
| /Linux-v5.4/Documentation/RCU/ |
| D | listRCU.rst | 143 a spin_lock() and a spin_unlock(), but in this case, all callers hold
|
| /Linux-v5.4/Documentation/scsi/ |
| D | libsas.txt | 384 and its callers, in the file "expander_conf.c".
|
| D | ChangeLog.megaraid | 606 viii. Optimize the build scatter-gather list routine. The callers already
|
| /Linux-v5.4/arch/sparc/kernel/ |
| D | entry.S | 897 mov %fp, %o1 ! yes, use callers usp
|
| /Linux-v5.4/Documentation/virt/kvm/ |
| D | mmu.txt | 311 reserved bit on the spte (see callers of kvm_mmu_set_mmio_spte_mask)
|
12
