Searched refs:callers (Results 1 – 25 of 49) sorted by relevance
12
| /linux-6.12.1/Documentation/mm/ |
| 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
|
| D | allocation-profiling.rst | 73 we'll generally want the accounting to happen in the callers of these helpers,
|
| D | highmem.rst | 122 sleep and the callers too may not sleep until after kunmap_atomic() is
|
| /linux-6.12.1/Documentation/networking/ |
| D | tc-actions-env-rules.rst | 23 The "environmental" rules for callers of actions (qdiscs etc) are:
|
| D | mctp.rst | 108 used; callers must set them to zero.
|
| /linux-6.12.1/drivers/scsi/ |
| 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-6.12.1/Documentation/filesystems/ |
| 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
|
| D | porting.rst | 121 check for ->link() target not being a directory is done by callers. Feel
128 ->link() callers hold ->i_mutex on the object we are linking to. Some of your
318 nobh_write_begin, blockdev_direct_IO*) to callers. Take a look at
319 ext2_write_failed and callers for an example.
781 is returned and callers reference to inode is subsumed by that. On
909 instead of passing mount and dentry separately. For callers that used to
928 callers never looked at specific -E... values anyway. -> iterate_shared()
938 changed to simplify callers. The passed file is in a non-open state and on
|
| 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-6.12.1/Documentation/userspace-api/media/dvb/ |
| D | dmx-fread.rst | 73 - The driver failed to write to the callers buffer due to an
|
| /linux-6.12.1/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.
|
| D | memory-allocation.rst | 115 that behavior so failures have to be checked properly by callers
|
| /linux-6.12.1/Documentation/arch/x86/ |
| D | amd_hsmp.rst | 42 * Locking across callers is taken care by the driver.
|
| /linux-6.12.1/Documentation/bpf/ |
| 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
|
| 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-6.12.1/Documentation/target/ |
| D | tcm_mod_builder.rst | 17 1) Generate new API callers for drivers/target/target_core_fabric_configs.c logic
|
| /linux-6.12.1/Documentation/driver-api/usb/ |
| D | dma.rst | 83 This may force your callers to do some bounce buffering, copying from
|
| /linux-6.12.1/Documentation/trace/ |
| D | events-kmem.rst | 66 callers should be batching their activities.
|
| /linux-6.12.1/Documentation/locking/ |
| D | mutex-design.rst | 119 release operation is still in progress - in other words, callers of
|
| /linux-6.12.1/kernel/dma/ |
| D | Kconfig | 268 Perform extra checking that callers of dma_map_sg() have respected the
|
| /linux-6.12.1/Documentation/process/ |
| D | deprecated.rst | 117 in callers. The respective kstrtol(), kstrtoll(),
141 for callers using only NUL-terminated strings.
|
| /linux-6.12.1/Documentation/rust/ |
| D | coding-guidelines.rst | 98 in code documentation. ``# Safety`` sections specify the contract that callers
|
| /linux-6.12.1/Documentation/driver-api/crypto/iaa/ |
| D | iaa-crypto.rst | 254 callers (e.g. zswap) wrap any asynchronous callees in a
258 support for callers that can make use of it. In this mode, it
|
| /linux-6.12.1/Documentation/scsi/ |
| D | libsas.rst | 447 and its callers, in the file "expander_conf.c".
|
12