Searched full:competing (Results 1 – 25 of 42) sorted by relevance
12
| /linux-6.14.4/Documentation/devicetree/bindings/i2c/ |
| D | i2c-gate.yaml | 16 there are no competing masters to consider for gates and therefore there is
|
| /linux-6.14.4/tools/sched_ext/ |
| D | scx_flatcg.bpf.c | 17 * For example, B is competing against C and in that competition its share is
18 * 100/(100+100) == 1/2. At its parent level, A is competing against D and A's
21 * eventual shaer is the same at 1/6. D is only competing at the top level and
25 * as B, C and D competing each other with respective share of 1/6, 1/6 and 2/3
32 * apache instances competing with 2:1 weight ratio nested four level deep.
|
| /linux-6.14.4/net/dccp/ccids/ |
| D | Kconfig | 20 be reasonably fair when competing for bandwidth with TCP-like flows,
|
| /linux-6.14.4/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-6.14.4/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-6.14.4/fs/jffs2/ |
| D | background.c | 108 * are generally competing for a higher latency resource - in jffs2_garbage_collect_thread()
|
| /linux-6.14.4/include/drm/ |
| D | drm_modeset_lock.h | 42 * Each thread competing for a set of locks must use one acquire
|
| /linux-6.14.4/Documentation/usb/ |
| D | CREDITS | 137 introductory documents (competing with Alberto's :).
|
| /linux-6.14.4/arch/mips/include/asm/ |
| D | sync.h | 140 * such that the Invalidate of a competing LL-SC goes 'missing' and SC
|
| /linux-6.14.4/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-6.14.4/Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 17 competing for the same channel.
|
| /linux-6.14.4/tools/testing/selftests/powerpc/mm/ |
| D | pkey_siginfo.c | 8 * attempted to be protected by two different keys from two competing
|
| /linux-6.14.4/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-6.14.4/Documentation/locking/ |
| D | ww-mutex-design.rst | 116 expect the number of simultaneous competing transactions to be typically small,
|
| /linux-6.14.4/Documentation/filesystems/caching/ |
| D | netfs-api.rst | 380 competing DIO writes to the same storage in the cache.
|
| /linux-6.14.4/Documentation/admin-guide/sysctl/ |
| D | net.rst | 144 RPS (e.g. RFS, aRFS) processing is competing with the registered NAPI poll function
|
| /linux-6.14.4/LICENSES/preferred/ |
| D | LGPL-2.1 | 98 advantage over competing non-free programs. These disadvantages are the
|
| /linux-6.14.4/fs/bcachefs/ |
| D | six.c | 114 * for anoter thread taking the competing lock type, and we may havve to do a
|
| /linux-6.14.4/block/ |
| D | blk-wbt.c | 545 * the idle limit, or go to normal if we haven't had competing in get_limit()
|
| /linux-6.14.4/drivers/memory/tegra/ |
| D | tegra20-emc.c | 1161 * competing memory accesses. This means that threshold should be in tegra_emc_devfreq_init()
|
| /linux-6.14.4/drivers/gpu/drm/i915/ |
| D | i915_active.c | 259 * worth competing to claim it atomically for ourselves (for in __active_lookup()
|
| /linux-6.14.4/drivers/clocksource/ |
| D | sh_cmt.c | 436 /* we're competing with the interrupt handler. in sh_cmt_clock_event_program_verify()
|
| /linux-6.14.4/mm/ |
| D | util.c | 1008 * balancing memory across competing virtual machines that are hosted.
|
| /linux-6.14.4/drivers/usb/core/ |
| D | urb.c | 179 * At this point, we could be competing with another thread which in usb_unanchor_urb()
|
| /linux-6.14.4/drivers/gpu/drm/amd/amdkfd/ |
| D | kfd_priv.h | 817 * number of CU's a device has along with number of other competing processes
|
12