Home
last modified time | relevance | path

Searched refs:small (Results 1 – 25 of 461) sorted by relevance

12345678910>>...19

/linux-6.1.9/lib/test_fortify/ !
Dtest_fortify.h22 char small[__BUF_SMALL]; variable
31 memset(small, 0xA5, sizeof(small)); in do_fortify_tests()
Dread_overflow-memchr_inv.c3 memchr_inv(small, 0x7A, sizeof(small) + 1)
Dread_overflow-memchr.c3 memchr(small, 0x7A, sizeof(small) + 1)
Dread_overflow-memscan.c3 memscan(small, 0x7A, sizeof(small) + 1)
Dread_overflow2-memcmp.c3 memcmp(large, small, sizeof(small) + 1)
Dwrite_overflow-strlcpy-src.c3 strlcpy(small, large_src, sizeof(small) + 1)
Dwrite_overflow-strncpy-src.c3 strncpy(small, large_src, sizeof(small) + 1)
Dread_overflow-memcmp.c3 memcmp(small, large, sizeof(small) + 1)
Dwrite_overflow-strcpy-lit.c3 strcpy(small, LITERAL_LARGE)
Dwrite_overflow-strcpy.c3 strcpy(small, large_src)
/linux-6.1.9/tools/testing/selftests/bpf/progs/ !
Dtest_global_func10.c26 const struct Small small = {.x = skb->len }; in test_cls() local
28 return foo((struct Big *)&small) ? 1 : 0; in test_cls()
/linux-6.1.9/drivers/mtd/spi-nor/ !
DKconfig14 bool "Use small 4096 B erase sectors"
17 Many flash memories support erasing small (4096 B) sectors. Depending
20 Changing a small part of the flash's contents is usually faster with
21 small sectors. On the other hand erasing should be faster when using
/linux-6.1.9/tools/testing/selftests/net/mptcp/ !
Dsimult_flows.sh27 rm -f "$large" "$small"
51 small=$(mktemp)
57 dd if=/dev/zero of=$small bs=4096 count=20 >/dev/null 2>&1
260 do_transfer $small $large $time
268 do_transfer $large $small $time
/linux-6.1.9/net/dccp/ccids/lib/ !
Dtfrc_equation.c591 static inline u32 tfrc_binsearch(u32 fval, u8 small) in tfrc_binsearch() argument
597 if (fval <= tfrc_calc_x_lookup[try][small]) in tfrc_binsearch()
/linux-6.1.9/fs/cramfs/ !
DKconfig7 System). CramFs is designed to be a simple, small, and compressed
20 purpose to remain small and low on RAM usage. It is most suitable
21 for small embedded systems. If you have ample RAM to spare, you may
/linux-6.1.9/arch/alpha/lib/ !
Dev6-copy_user.S50 subq $18, 32, $1 # .. .. E. .. : Is this going to be a small copy?
55 ble $1, $onebyteloop # .. .. U .. : 1st branch : small amount of data
131 subq $4, 32, $2 # .. .. .. E : do not unroll for small stuff
/linux-6.1.9/Documentation/gpu/rfc/ !
Di915_small_bar.rst14 underneath the device has a small BAR, meaning only some portion of it is CPU
41 1) Error capture is best effort on small BAR systems; if the pages are not
/linux-6.1.9/Documentation/networking/ !
Dsmc-sysctl.rst13 perspective of view. When applications do consecutive small
14 write()/sendmsg() system calls, we try to coalesce these small writes
/linux-6.1.9/Documentation/ABI/testing/ !
Dsysfs-class-chromeos-driver-cros-ec-vbc6 small nvram space on some EC implementations.
Dsysfs-bus-iio-light-si11336 dark photodiode. "small" indicate the surface area capturing
/linux-6.1.9/Documentation/trace/ !
Devents-kmem.rst8 - Slab allocation of small objects of unknown type (kmalloc)
9 - Slab allocation of small objects of known type
17 1. Slab allocation of small objects of unknown type
32 2. Slab allocation of small objects of known type
/linux-6.1.9/Documentation/filesystems/ !
Dromfs.rst10 similar feature, and even the possibility of a small kernel, with a
30 However, the main purpose of romfs is to have a very small kernel,
41 module. The kernel can be small enough, since it doesn't have other
154 this file system is the small code. On the other hand, don't be
171 - The file system is read only, so it can be very small, but in case
175 similarly small writable filesystem for RAM disks.
/linux-6.1.9/arch/x86/include/asm/ !
Dpage_64.h93 [small] "i" ((1ul << 47)-PAGE_SIZE), in task_size_max()
/linux-6.1.9/drivers/atm/ !
Dnicstarmac.copyright25 * IDT always receives data into a small buffer, then large buffers
30 * copy small buffer contents to head of large buffer.
/linux-6.1.9/arch/arm/mach-lpc32xx/ !
Dsuspend.S51 @ This guarantees a small windows where DRAM isn't busy

12345678910>>...19