Home
last modified time | relevance | path

Searched full:sufficient (Results 1 – 25 of 689) sorted by relevance

12345678910>>...28

/Linux-v5.4/net/core/
Dgen_stats.c56 * Returns 0 on success or -1 if the room in the socket buffer was not sufficient.
107 * Returns 0 on success or -1 if the room in the socket buffer was not sufficient.
200 * if the room in the socket buffer was not sufficient.
224 * if the room in the socket buffer was not sufficient.
246 * if the room in the socket buffer was not sufficient.
329 * if the room in the socket buffer was not sufficient.
367 * if the room in the socket buffer was not sufficient.
403 * if the room in the socket buffer was not sufficient.
/Linux-v5.4/tools/include/linux/
Dring_buffer.h34 * For B a WMB is sufficient since it separates two WRITEs,
35 * and for C an RMB is sufficient since it separates two READs.
/Linux-v5.4/sound/pci/ctxfi/
Dctresource.c28 /* Check whether there are sufficient resources to meet request. */ in get_resource()
37 break; /* found sufficient contiguous resources */ in get_resource()
41 /* Can not find sufficient contiguous resources */ in get_resource()
/Linux-v5.4/fs/jfs/
Djfs_dmap.c753 * AG with sufficient free space. in dbAlloc()
1223 * check the next four contiguous leaves for sufficient free
1224 * space. if sufficient free space is found, we'll allocate
1264 /* examine the leaves for sufficient free space. in dbAllocNear()
1267 /* does the leaf describe sufficient free space ? in dbAllocNear()
1317 * sufficient free space. if sufficient free space is found,
1323 * sufficient free space and we allocate at this dmap.
1423 * the allocation group, looking for sufficient free space. to begin, in dbAllocAG()
1436 * subtrees for sufficient free space, starting with the leftmost in dbAllocAG()
1440 /* is there sufficient free space ? in dbAllocAG()
[all …]
/Linux-v5.4/arch/riscv/include/asm/
Dmmiowb.h7 * "o,w" is sufficient to ensure that all writes to the device have completed
/Linux-v5.4/tools/build/feature/
Dtest-libopencsd.c5 * Check OpenCSD library version is sufficient to provide required features
/Linux-v5.4/arch/m68k/ifpsp060/src/
DREADME-SRC11 are sufficient and were generated from these source files by
/Linux-v5.4/tools/memory-model/litmus-tests/
DREADME26 sufficient to cause two different reading processes to agree on
141 spin_lock() sufficient to make ordering apparent to accesses
149 Is the ordering provided by a release-acquire chain sufficient
DMP+pooncerelease+poacquireonce.litmus7 * smp_load_acquire() provide sufficient ordering for the message-passing
DMP+fencewmbonceonce+fencermbonceonce.litmus7 * sufficient ordering for the message-passing pattern. However, it
DIRIW+fencembonceonces+OnceOnce.litmus7 * between each pairs of reads. In other words, is smp_mb() sufficient to
DZ6.0+pooncerelease+poacquirerelease+fencembonceonce.litmus6 * This litmus test shows that a release-acquire chain, while sufficient
/Linux-v5.4/Documentation/ABI/stable/
Do2cb9 Users: ocfs2-tools. It's sufficient to mail proposed changes to
/Linux-v5.4/Documentation/ABI/removed/
Do2cb9 Users: ocfs2-tools. It's sufficient to mail proposed changes to
/Linux-v5.4/Documentation/devicetree/bindings/sound/
Dmax98357a.txt15 It's observed that 5ms is sufficient.
Dmax98373.txt25 for the I/V sense data is not sufficient, the device can also be configured
/Linux-v5.4/drivers/target/iscsi/
Discsi_target_auth.h13 #define MAX_RESPONSE_LENGTH 64 /* sufficient for MD5 */
/Linux-v5.4/Documentation/admin-guide/mm/
Dhugetlbpage.rst127 allocating extra pages on other nodes with sufficient available contiguous
226 However, if a node in the policy does not contain sufficient contiguous
228 neighbor node with sufficient contiguous memory. To do this would cause
281 pages on the parent node will be adjusted to the specified value, if sufficient
/Linux-v5.4/drivers/gpu/drm/i915/gt/
Dintel_renderstate.c64 * this is sufficient as the null state generator makes the final batch
67 * right after the commands taking care of alignment so we should sufficient
/Linux-v5.4/include/crypto/
Dhash.h460 * @out: output buffer of sufficient size that can hold the hash state
463 * caller-allocated output buffer out which must have sufficient size (e.g. by
651 * ensure that the buffer has sufficient space by, for example, calling
793 * sufficient memory for operational state.
848 * @out: output buffer of sufficient size that can hold the hash state
851 * caller-allocated output buffer out which must have sufficient size (e.g. by
/Linux-v5.4/Documentation/media/uapi/dvb/
Dfe-read-snr.rst45 to the device is sufficient.
Dfe-read-ber.rst45 access to the device is sufficient.
/Linux-v5.4/tools/arch/powerpc/include/asm/
Dbarrier.h23 * operations with one another. sync is the only instruction sufficient
/Linux-v5.4/fs/ramfs/
Dfile-mmu.c24 * caches is sufficient.
/Linux-v5.4/include/uapi/scsi/
Dscsi_bsg_fc.h78 * There is no additional response data - fc_bsg_reply->result is sufficient
99 * There is no additional response data - fc_bsg_reply->result is sufficient

12345678910>>...28