| /linux/Documentation/mm/ |
| H A D | page_frags.rst | 26 allocation. The netdev_alloc_cache is used by callers making use of the
28 used by callers of the __napi_alloc_frag and napi_alloc_skb calls. The
|
| H A D | allocation-profiling.rst | 73 we'll generally want the accounting to happen in the callers of these helpers,
|
| H A D | highmem.rst | 122 sleep and the callers too may not sleep until after kunmap_atomic() is
|
| /linux/drivers/scsi/ |
| H A D | xen-scsifront.c | 129 unsigned callers; member
589 info->callers++; in scsifront_enter()
595 info->callers--; in scsifront_return()
596 if (info->callers) in scsifront_return()
985 while (info->callers && !err) { in scsifront_suspend()
|
| /linux/Documentation/networking/ |
| H A D | tc-actions-env-rules.rst | 23 The "environmental" rules for callers of actions (qdiscs etc) are:
|
| H A D | mctp.rst | 108 used; callers must set them to zero.
|
| /linux/Documentation/filesystems/ |
| H A D | files.rst | 113 words, callers might see reference count bumps from newer users. For
121 in struct file. With SLAB_TYPESAFE_BY_RCU it is necessary that callers
|
| H A D | path-lookup.rst | 474 component remains for the caller to sort out. Those callers are
1171 For some callers, this is all they need; they want to create that
1173 callers will want to follow a symlink if one is found, and possibly
1175 than just the last component of the original file name. These callers
1180 This case is handled by relevant callers of link_path_walk(), such as
1370 Various callers set this and it is also set when the final component
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | dmx-fread.rst | 73 - The driver failed to write to the callers buffer due to an
|
| /linux/Documentation/core-api/ |
| H A D | debug-objects.rst | 85 on the callers stack. If it is on the callers stack then a limited
108 the callers stack.
|
| H A D | timekeeping.rst | 73 more convenient for some callers.
|
| H A D | memory-allocation.rst | 115 that behavior so failures have to be checked properly by callers
|
| /linux/Documentation/arch/x86/ |
| H A D | amd_hsmp.rst | 42 * Locking across callers is taken care by the driver.
|
| /linux/Documentation/bpf/ |
| H A D | cpumasks.rst | 255 complementary kfuncs that allow callers to atomically test and set (or clear)
273 callers can also perform bitwise operations between multiple cpumasks using
|
| H A D | kfuncs.rst | 441 refactoring cannot typically change callers in-place when a kfunc changes,
636 bpf_cgroup_ancestor() and bpf_cgroup_from_id(), allowing callers to access
|
| /linux/Documentation/driver-api/usb/ |
| H A D | dma.rst | 83 This may force your callers to do some bounce buffering, copying from
|
| /linux/Documentation/target/ |
| H A D | tcm_mod_builder.rst | 17 1) Generate new API callers for drivers/target/target_core_fabric_configs.c logic
|
| /linux/Documentation/trace/ |
| H A D | events-kmem.rst | 66 callers should be batching their activities.
|
| /linux/Documentation/locking/ |
| H A D | mutex-design.rst | 119 release operation is still in progress - in other words, callers of
|
| H A D | locktypes.rst | 370 local_lock_1 and local_lock_2 are distinct and cannot serialize the callers
|
| /linux/kernel/dma/ |
| H A D | Kconfig | 268 Perform extra checking that callers of dma_map_sg() have respected the
|
| /linux/Documentation/process/ |
| H A D | deprecated.rst | 117 in callers. The respective kstrtol(), kstrtoll(),
141 for callers using only NUL-terminated strings.
|
| /linux/Documentation/rust/ |
| H A D | coding-guidelines.rst | 98 in code documentation. ``# Safety`` sections specify the contract that callers
|
| /linux/Documentation/scsi/ |
| H A D | libsas.rst | 447 and its callers, in the file "expander_conf.c".
|
| /linux/tools/perf/Documentation/ |
| H A D | perf-top.txt | 212 This has the effect of collecting the callers of each such
|