Home
last modified time | relevance | path

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

/Linux-v4.19/drivers/gpu/drm/msm/disp/
Dmdp_format.c74 #define FMT(name, a, r, g, b, e0, e1, e2, e3, alpha, tight, c, cnt, fp, cs, yuv) { \ argument
82 .unpack_tight = tight, \
/Linux-v4.19/drivers/iio/trigger/
DKconfig53 Uses a tight loop in a kthread. Will only work with lower half only
/Linux-v4.19/drivers/staging/erofs/
Dunzip_vle.c598 bool tight = builder_is_followed(builder); in z_erofs_do_read_page() local
662 tight &= builder_is_followed(builder); in z_erofs_do_read_page()
674 (tight ? Z_EROFS_PAGE_TYPE_EXCLUSIVE : in z_erofs_do_read_page()
/Linux-v4.19/Documentation/filesystems/
Dcramfs.txt63 handy for tiny embedded systems with very tight memory constraints.
Daffs.txt201 is also true when space gets tight.
/Linux-v4.19/drivers/net/wireless/intel/iwlwifi/
DKconfig99 a tight integration with the platform. It is not recommended
/Linux-v4.19/Documentation/block/
Dbfq-iosched.txt111 guarantees, it is possible to compute tight per-I/O-request delay
222 - B-WF2Q+ guarantees a tight deviation with respect to an ideal,
236 BFQ can keep this deviation tight not only because of the
246 tight latency guarantees to time-sensitive applications. When
/Linux-v4.19/Documentation/fb/
Dudlfb.txt36 tight relative to the functionality it provides.
/Linux-v4.19/Documentation/
Drtc.txt75 typical 486-33 running a tight read loop on /dev/rtc will start to suffer
/Linux-v4.19/Documentation/timers/
Dhrtimers.txt25 code is very good and tight code, there's zero problems with it in its
/Linux-v4.19/Documentation/driver-api/usb/
DURB.rst142 allocation, such as whether the lower levels may block when memory is tight.
/Linux-v4.19/Documentation/sound/designs/
Dcompress-offload.rst206 API. Support for dynamic bit-rate changes would require a tight
/Linux-v4.19/Documentation/networking/
Dixgbe.txt125 different queues. Enables tight control on routing a flow in the platform.
Dz8530book.rst30 extremely tight timing requirements. Doing high speeds, even with a
/Linux-v4.19/Documentation/security/
Dself-protection.rst45 the kernel needs to protect its memory with a tight set of permissions.
/Linux-v4.19/kernel/trace/
DKconfig673 As it is a tight loop, it benchmarks as hot cache. That's fine because
/Linux-v4.19/Documentation/admin-guide/
Dcgroup-v2.rst979 While not completely water-tight, all major memory usages by a given
2135 anonymous memory in a tight loop - and an admin can not assume full
/Linux-v4.19/Documentation/media/uapi/v4l/
Dextended-controls.rst1566 #. For tight CBR, this field must be small (ex. 2 ~ 10). For
1635 will meet tight bandwidth constraints. Applicable to encoders.