Home
last modified time | relevance | path

Searched full:competing (Results 1 – 25 of 30) sorted by relevance

12

/linux/Documentation/devicetree/bindings/i2c/
H A Di2c-gate.yaml16 there are no competing masters to consider for gates and therefore there is
/linux/tools/sched_ext/
H A Dscx_flatcg.bpf.c17 * 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 share 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/net/dccp/ccids/
H A DKconfig
/linux/tools/testing/selftests/bpf/benchs/
H A Drun_bench_ringbufs.sh42 header "Single-producer, consumer/producer competing on the same CPU, low batch count"
/linux/Documentation/
H A Datomic_t.txt115 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/include/drm/
H A Ddrm_modeset_lock.h42 * Each thread competing for a set of locks must use one acquire
/linux/arch/mips/include/asm/
H A Dsync.h140 * such that the Invalidate of a competing LL-SC goes 'missing' and SC
/linux/tools/testing/selftests/sched_ext/
H A Drt_stall.c141 * competing with the RT task (small 1% fluctuations are expected). in sched_stress_test()
/linux/drivers/nvdimm/
H A Dpmem.c334 * caches and finally write. A competing pread thread will be held
337 * the recovery write is complete. Competing recovery write threads
/linux/Documentation/driver-api/dmaengine/
H A Ddmatest.rst17 competing for the same channel.
/linux/Documentation/block/
H A Dbfq-iosched.rst194 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/Documentation/locking/
H A Dww-mutex-design.rst116 expect the number of simultaneous competing transactions to be typically small,
/linux/Documentation/filesystems/caching/
H A Dnetfs-api.rst380 competing DIO writes to the same storage in the cache.
/linux/LICENSES/preferred/
H A DLGPL-2.1102 advantage over competing non-free programs. These disadvantages are the
/linux/block/
H A Dblk-wbt.c549 * the idle limit, or go to normal if we haven't had competing in get_limit()
/linux/drivers/gpu/drm/i915/
H A Di915_active.c259 * worth competing to claim it atomically for ourselves (for in __active_lookup()
/linux/drivers/usb/core/
H A Durb.c178 * At this point, we could be competing with another thread which in usb_unanchor_urb()
/linux/tools/testing/vma/include/
H A Ddup.h1193 * has been isolated under mmap_write_lock, ensuring no competing writers.
/linux/Documentation/cdrom/
H A Dcdrom-standard.rst667 deal with a dozen or more different, competing hardware
/linux/drivers/accel/habanalabs/common/
H A Ddevice.c2498 * This function is competing with the reset function, so try to in hl_device_fini()
/linux/fs/
H A Dfs-writeback.c968 * If there are multiple closely competing dirtiers, the in wbc_detach_inode()
/linux/Documentation/scsi/
H A Dncr53c8xx.rst1239 competing for the SCSI BUS. By the way, when the chip is using SCSI id 7,
/linux/kernel/cgroup/
H A Dcpuset.c3833 * and so there shouldn't be a competing cpuset_attach() operation. in cpuset_fork()
/linux/Documentation/admin-guide/
H A Dcgroup-v2.rst3449 constantly changed as the number of competing entities fluctuated.
/linux/drivers/clk/
H A Dclk.c2678 * satisfied when several consumers are competing for exclusivity over the

12