Searched full:competing (Results 1 – 25 of 41) sorted by relevance
12
| /Linux-v6.6/Documentation/devicetree/bindings/i2c/ |
| D | i2c-gate.yaml | 16 there are no competing masters to consider for gates and therefore there is
|
| /Linux-v6.6/net/dccp/ccids/ |
| D | Kconfig | 20 be reasonably fair when competing for bandwidth with TCP-like flows,
|
| /Linux-v6.6/tools/testing/selftests/bpf/benchs/ |
| D | run_bench_ringbufs.sh | 42 header "Single-producer, consumer/producer competing on the same CPU, low batch count"
|
| /Linux-v6.6/Documentation/ |
| D | atomic_t.txt | 115 This is typically true on 'normal' platforms, where a regular competing STORE
328 guarantees between competing LL/SC sections, such a guarantee does not
|
| /Linux-v6.6/fs/jffs2/ |
| D | background.c | 108 * are generally competing for a higher latency resource - in jffs2_garbage_collect_thread()
|
| /Linux-v6.6/include/drm/ |
| D | drm_modeset_lock.h | 42 * Each thread competing for a set of locks must use one acquire
|
| /Linux-v6.6/Documentation/usb/ |
| D | CREDITS | 137 introductory documents (competing with Alberto's :).
|
| /Linux-v6.6/arch/mips/include/asm/ |
| D | sync.h | 140 * such that the Invalidate of a competing LL-SC goes 'missing' and SC
|
| /Linux-v6.6/drivers/nvdimm/ |
| D | pmem.c | 320 * caches and finally write. A competing pread thread will be held
323 * the recovery write is complete. Competing recovery write threads
|
| /Linux-v6.6/Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 17 competing for the same channel.
|
| /Linux-v6.6/tools/testing/selftests/powerpc/mm/ |
| D | pkey_siginfo.c | 8 * attempted to be protected by two different keys from two competing
|
| /Linux-v6.6/fs/9p/ |
| D | vfs_addr.c | 287 * there's more than one writer competing for the same cache block. in v9fs_write_begin()
|
| /Linux-v6.6/drivers/gpu/drm/nouveau/ |
| D | nouveau_sched.c | 18 * other jobs competing for the hardware. Otherwise we might end up with job
|
| /Linux-v6.6/Documentation/block/ |
| D | bfq-iosched.rst | 194 processes are competing for the device at the same time, but
282 - If several processes are competing for the device at the same time,
|
| /Linux-v6.6/Documentation/locking/ |
| D | ww-mutex-design.rst | 116 expect the number of simultaneous competing transactions to be typically small,
|
| /Linux-v6.6/Documentation/filesystems/caching/ |
| D | netfs-api.rst | 380 competing DIO writes to the same storage in the cache.
|
| /Linux-v6.6/Documentation/admin-guide/sysctl/ |
| D | net.rst | 142 RPS (e.g. RFS, aRFS) processing is competing with the registered NAPI poll function
|
| /Linux-v6.6/LICENSES/preferred/ |
| D | LGPL-2.1 | 98 advantage over competing non-free programs. These disadvantages are the
|
| /Linux-v6.6/block/ |
| D | blk-wbt.c | 546 * the idle limit, or go to normal if we haven't had competing in get_limit()
|
| /Linux-v6.6/fs/afs/ |
| D | write.c | 85 * there's more than one writer competing for the same cache block. in afs_write_begin()
|
| /Linux-v6.6/drivers/gpu/drm/i915/ |
| D | i915_active.c | 259 * worth competing to claim it atomically for ourselves (for in __active_lookup()
|
| /Linux-v6.6/mm/ |
| D | util.c | 900 * balancing memory across competing virtual machines that are hosted.
|
| /Linux-v6.6/drivers/clocksource/ |
| D | sh_cmt.c | 436 /* we're competing with the interrupt handler. in sh_cmt_clock_event_program_verify()
|
| /Linux-v6.6/drivers/memory/tegra/ |
| D | tegra20-emc.c | 1164 * competing memory accesses. This means that threshold should be in tegra_emc_devfreq_init()
|
| /Linux-v6.6/drivers/usb/core/ |
| D | urb.c | 179 * At this point, we could be competing with another thread which in usb_unanchor_urb()
|
12
