| /linux/drivers/gpu/drm/msm/disp/ |
| A D | mdp_format.c | 63 #define FMT(name, a, r, g, b, e0, e1, e2, e3, alpha, tight, c, cnt, fp, cs, yuv) { \ argument
71 .unpack_tight = tight, \
|
| /linux/fs/erofs/ |
| A D | zdata.c | 640 bool tight = true; in z_erofs_do_read_page() local
700 tight &= (clt->mode >= COLLECT_PRIMARY_HOOKED && in z_erofs_do_read_page()
712 (tight ? Z_EROFS_PAGE_TYPE_EXCLUSIVE : in z_erofs_do_read_page()
716 tight &= (clt->mode >= COLLECT_PRIMARY_FOLLOWED); in z_erofs_do_read_page()
|
| /linux/drivers/iio/trigger/ |
| A D | Kconfig | 54 Uses a tight loop in a kthread. Will only work with lower half only
|
| /linux/Documentation/filesystems/ |
| A D | cramfs.rst | 66 handy for tiny embedded systems with very tight memory constraints.
|
| A D | affs.rst | 229 is also true when space gets tight.
|
| /linux/Documentation/block/ |
| A D | bfq-iosched.rst | 132 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/Documentation/userspace-api/ |
| A D | iommu.rst | 121 In this tight-knit VFIO-IOMMU interface, the ultimate consumer of the
|
| /linux/Documentation/power/ |
| A D | energy-model.rst | 120 cpufreq_register_em_with_opp(). It implements a power model which is tight to
|
| /linux/Documentation/fb/ |
| A D | udlfb.rst | 36 tight relative to the functionality it provides.
|
| /linux/Documentation/admin-guide/ |
| A D | rtc.rst | 75 typical 486-33 running a tight read loop on /dev/rtc will start to suffer
|
| A D | cgroup-v2.rst | 1101 While not completely water-tight, all major memory usages by a given
2823 anonymous memory in a tight loop - and an admin can not assume full
|
| /linux/Documentation/timers/ |
| A D | hrtimers.rst | 25 code is very good and tight code, there's zero problems with it in its
|
| /linux/Documentation/sound/designs/ |
| A D | compress-offload.rst | 289 API. Support for dynamic bit-rate changes would require a tight
|
| /linux/Documentation/driver-api/usb/ |
| A D | URB.rst | 142 allocation, such as whether the lower levels may block when memory is tight.
|
| /linux/Documentation/networking/device_drivers/wan/ |
| A D | z8530book.rst | 30 extremely tight timing requirements. Doing high speeds, even with a
|
| /linux/Documentation/security/ |
| A D | self-protection.rst | 45 the kernel needs to protect its memory with a tight set of permissions.
|
| /linux/Documentation/networking/dsa/ |
| A D | sja1105.rst | 225 tight timing-based admission control for up to 1024 flows (identified by a
|
| /linux/Documentation/networking/device_drivers/ethernet/intel/ |
| A D | ixgbe.rst | 317 - Enables tight control on routing a flow in the platform.
|
| A D | i40e.rst | 128 - Enables tight control on routing a flow in the platform.
|
| A D | ice.rst | 213 - Enables tight control on routing a flow in the platform
|
| /linux/Documentation/RCU/Design/Expedited-Grace-Periods/ |
| A D | Expedited-Grace-Periods.rst | 505 tight synchronization between expedited grace periods and CPU-hotplug
|
| /linux/Documentation/userspace-api/media/v4l/ |
| A D | ext-ctrls-codec.rst | 1714 #. For tight CBR, this field must be small (ex. 2 ~ 10). For
1794 will meet tight bandwidth constraints. Applicable to encoders.
|
| /linux/kernel/trace/ |
| A D | Kconfig | 773 As it is a tight loop, it benchmarks as hot cache. That's fine because
|
| /linux/Documentation/RCU/Design/Requirements/ |
| A D | Requirements.rst | 1425 CPUs 1 through 63 spin in tight loops that invoke call_rcu(). Even
1426 if these tight loops also contain calls to cond_resched() (thus
1570 tight loop in the early 2000s suddenly provided a much deeper
|
| /linux/Documentation/admin-guide/pm/ |
| A D | cpuidle.rst | 629 more or less "lightweight" sequence of instructions in a tight loop. [Note
|