Home
last modified time | relevance | path

Searched refs:callers (Results 1 – 25 of 43) sorted by relevance

12

/Linux-v6.1/Documentation/mm/
Dpage_frags.rst28 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
Dhighmem.rst109 sleep and the callers too may not sleep until after kunmap_atomic() is
/Linux-v6.1/Documentation/networking/
Dtc-actions-env-rules.rst23 The "environmental" rules for callers of actions (qdiscs etc) are:
Dmctp.rst108 used; callers must set them to zero.
/Linux-v6.1/drivers/scsi/
Dxen-scsifront.c129 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-v6.1/Documentation/userspace-api/media/dvb/
Ddmx-fread.rst73 - The driver failed to write to the callers buffer due to an
/Linux-v6.1/Documentation/filesystems/
Dporting.rst121 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.
786 is returned and callers reference to inode is subsumed by that. On
914 instead of passing mount and dentry separately. For callers that used to
933 callers never looked at specific -E... values anyway. ->iterate() and
943 changed to simplify callers. The passed file is in a non-open state and on
Dpath-lookup.rst474 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-v6.1/Documentation/x86/
Damd_hsmp.rst41 * Locking across callers is taken care by the driver.
/Linux-v6.1/Documentation/core-api/
Ddebug-objects.rst85 on the callers stack. If it is on the callers stack then a limited
108 the callers stack.
Dtimekeeping.rst73 more convenient for some callers.
Dmemory-allocation.rst114 that behavior so failures have to be checked properly by callers
/Linux-v6.1/Documentation/target/
Dtcm_mod_builder.rst17 1) Generate new API callers for drivers/target/target_core_fabric_configs.c logic
/Linux-v6.1/Documentation/trace/
Devents-kmem.rst66 callers should be batching their activities.
/Linux-v6.1/kernel/dma/
DKconfig225 Perform extra checking that callers of dma_map_sg() have respected the
/Linux-v6.1/Documentation/driver-api/usb/
Ddma.rst83 This may force your callers to do some bounce buffering, copying from
/Linux-v6.1/Documentation/process/
Ddeprecated.rst117 in callers. The respective kstrtol(), kstrtoll(),
141 for callers using only NUL-terminated strings.
/Linux-v6.1/drivers/block/paride/
DTransition-notes128 can be taken to callers as long as they remain within the area.
/Linux-v6.1/Documentation/rust/
Dcoding-guidelines.rst98 in code documentation. ``# Safety`` sections specify the contract that callers
/Linux-v6.1/Documentation/userspace-api/
Diommu.rst198 provided to distinguish the callers. For example,
/Linux-v6.1/Documentation/scsi/
Dlibsas.rst447 and its callers, in the file "expander_conf.c".
/Linux-v6.1/tools/perf/Documentation/
Dperf-top.txt205 This has the effect of collecting the callers of each such
/Linux-v6.1/Documentation/locking/
Dlocktypes.rst370 local_lock_1 and local_lock_2 are distinct and cannot serialize the callers
/Linux-v6.1/Documentation/RCU/
DlistRCU.rst192 spin_lock() and a spin_unlock(). But in this case, all callers hold
/Linux-v6.1/Documentation/block/
Dinline-encryption.rst148 For encryption, the data cannot be encrypted in-place, as callers usually rely

12