Searched refs:tight (Results 1 – 25 of 25) sorted by relevance
63 #define FMT(name, a, r, g, b, e0, e1, e2, e3, alpha, tight, c, cnt, fp, cs, yuv) { \ argument71 .unpack_tight = tight, \
54 Uses a tight loop in a kthread. Will only work with lower half only
653 bool tight = true; in z_erofs_do_read_page() local713 tight &= (clt->mode >= COLLECT_PRIMARY_HOOKED && in z_erofs_do_read_page()725 (tight ? Z_EROFS_PAGE_TYPE_EXCLUSIVE : in z_erofs_do_read_page()729 tight &= (clt->mode >= COLLECT_PRIMARY_FOLLOWED); in z_erofs_do_read_page()
66 handy for tiny embedded systems with very tight memory constraints.
229 is also true when space gets tight.
132 guarantees, it is possible to compute tight per-I/O-request delay243 - B-WF2Q+ guarantees a tight deviation with respect to an ideal,257 BFQ can keep this deviation tight not only because of the267 tight latency guarantees to time-sensitive applications. When
36 tight relative to the functionality it provides.
121 In this tight-knit VFIO-IOMMU interface, the ultimate consumer of the
75 typical 486-33 running a tight read loop on /dev/rtc will start to suffer
1093 While not completely water-tight, all major memory usages by a given2805 anonymous memory in a tight loop - and an admin can not assume full
4587 period to do tight-loop forward-progress testing.4595 need_resched() during tight-loop forward-progress
25 code is very good and tight code, there's zero problems with it in its
289 API. Support for dynamic bit-rate changes would require a tight
142 allocation, such as whether the lower levels may block when memory is tight.
45 the kernel needs to protect its memory with a tight set of permissions.
30 extremely tight timing requirements. Doing high speeds, even with a
225 tight timing-based admission control for up to 1024 flows (identified by a
317 - Enables tight control on routing a flow in the platform.
128 - Enables tight control on routing a flow in the platform.
213 - Enables tight control on routing a flow in the platform
505 tight synchronization between expedited grace periods and CPU-hotplug
1714 #. For tight CBR, this field must be small (ex. 2 ~ 10). For1794 will meet tight bandwidth constraints. Applicable to encoders.
773 As it is a tight loop, it benchmarks as hot cache. That's fine because
1425 CPUs 1 through 63 spin in tight loops that invoke call_rcu(). Even1426 if these tight loops also contain calls to cond_resched() (thus1570 tight loop in the early 2000s suddenly provided a much deeper
629 more or less "lightweight" sequence of instructions in a tight loop. [Note
