Home
last modified time | relevance | path

Searched refs:tight (Results 1 – 20 of 20) sorted by relevance

/Linux-v5.4/drivers/gpu/drm/msm/disp/
Dmdp_format.c63 #define FMT(name, a, r, g, b, e0, e1, e2, e3, alpha, tight, c, cnt, fp, cs, yuv) { \ argument
71 .unpack_tight = tight, \
/Linux-v5.4/drivers/iio/trigger/
DKconfig54 Uses a tight loop in a kthread. Will only work with lower half only
/Linux-v5.4/fs/erofs/
Dzdata.c578 bool tight = true; in z_erofs_do_read_page() local
638 tight &= (clt->mode >= COLLECT_PRIMARY_HOOKED && in z_erofs_do_read_page()
650 (tight ? Z_EROFS_PAGE_TYPE_EXCLUSIVE : in z_erofs_do_read_page()
654 tight &= (clt->mode >= COLLECT_PRIMARY_FOLLOWED); in z_erofs_do_read_page()
/Linux-v5.4/Documentation/filesystems/
Dcramfs.txt63 handy for tiny embedded systems with very tight memory constraints.
Daffs.txt201 is also true when space gets tight.
/Linux-v5.4/Documentation/block/
Dbfq-iosched.rst132 guarantees, it is possible to compute tight per-I/O-request delay
243 - B-WF2Q+ guarantees a tight deviation with respect to an ideal,
257 BFQ can keep this deviation tight not only because of the
267 tight latency guarantees to time-sensitive applications. When
/Linux-v5.4/Documentation/fb/
Dudlfb.rst36 tight relative to the functionality it provides.
/Linux-v5.4/Documentation/admin-guide/
Drtc.rst75 typical 486-33 running a tight read loop on /dev/rtc will start to suffer
Dcgroup-v2.rst1063 While not completely water-tight, all major memory usages by a given
2538 anonymous memory in a tight loop - and an admin can not assume full
Dkernel-parameters.txt3999 period to do tight-loop forward-progress testing.
4007 need_resched() during tight-loop forward-progress
/Linux-v5.4/Documentation/timers/
Dhrtimers.rst25 code is very good and tight code, there's zero problems with it in its
/Linux-v5.4/Documentation/sound/designs/
Dcompress-offload.rst206 API. Support for dynamic bit-rate changes would require a tight
/Linux-v5.4/Documentation/driver-api/usb/
DURB.rst142 allocation, such as whether the lower levels may block when memory is tight.
/Linux-v5.4/Documentation/security/
Dself-protection.rst45 the kernel needs to protect its memory with a tight set of permissions.
/Linux-v5.4/Documentation/networking/
Dz8530book.rst30 extremely tight timing requirements. Doing high speeds, even with a
/Linux-v5.4/Documentation/networking/device_drivers/intel/
Dixgbe.rst317 - Enables tight control on routing a flow in the platform.
Di40e.rst128 - Enables tight control on routing a flow in the platform.
/Linux-v5.4/kernel/trace/
DKconfig692 As it is a tight loop, it benchmarks as hot cache. That's fine because
/Linux-v5.4/Documentation/media/uapi/v4l/
Dext-ctrls-codec.rst2709 #. For tight CBR, this field must be small (ex. 2 ~ 10). For
2784 will meet tight bandwidth constraints. Applicable to encoders.
/Linux-v5.4/Documentation/admin-guide/pm/
Dcpuidle.rst693 more or less ``lightweight'' sequence of instructions in a tight loop. [Note