Searched refs:tight (Results 1 – 24 of 24) sorted by relevance
/linux-6.12.1/fs/erofs/ |
D | zdata.c | 918 bool tight, excl; in z_erofs_scan_folio() local 921 tight = (bs == PAGE_SIZE); in z_erofs_scan_folio() 941 tight = false; in z_erofs_scan_folio() 950 tight = false; in z_erofs_scan_folio() 967 tight &= (f->mode >= Z_EROFS_PCLUSTER_FOLLOWED); in z_erofs_scan_folio() 970 excl = (split <= 1) || tight; in z_erofs_scan_folio() 998 tight = (bs == PAGE_SIZE); in z_erofs_scan_folio()
|
/linux-6.12.1/drivers/iio/trigger/ |
D | Kconfig | 54 Uses a tight loop in a kthread. Will only work with lower half only
|
/linux-6.12.1/Documentation/filesystems/ |
D | cramfs.rst | 66 handy for tiny embedded systems with very tight memory constraints.
|
D | affs.rst | 229 is also true when space gets tight.
|
/linux-6.12.1/Documentation/block/ |
D | bfq-iosched.rst | 132 guarantees, it is possible to compute a 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-6.12.1/Documentation/fb/ |
D | udlfb.rst | 36 tight relative to the functionality it provides.
|
/linux-6.12.1/Documentation/admin-guide/ |
D | rtc.rst | 75 typical 486-33 running a tight read loop on /dev/rtc will start to suffer
|
D | cgroup-v2.rst | 1205 While not completely water-tight, all major memory usages by a given 3231 anonymous memory in a tight loop - and an admin can not assume full
|
D | kernel-parameters.txt | 5340 period to do tight-loop forward-progress testing. 5348 need_resched() during tight-loop forward-progress
|
/linux-6.12.1/Documentation/timers/ |
D | hrtimers.rst | 25 code is very good and tight code, there's zero problems with it in its
|
/linux-6.12.1/Documentation/driver-api/usb/ |
D | URB.rst | 142 allocation, such as whether the lower levels may block when memory is tight.
|
/linux-6.12.1/Documentation/sound/designs/ |
D | compress-offload.rst | 290 API. Support for dynamic bit-rate changes would require a tight
|
/linux-6.12.1/Documentation/security/ |
D | self-protection.rst | 45 the kernel needs to protect its memory with a tight set of permissions.
|
/linux-6.12.1/Documentation/power/ |
D | energy-model.rst | 175 cpufreq_register_em_with_opp(). It implements a power model which is tight to
|
/linux-6.12.1/Documentation/networking/dsa/ |
D | sja1105.rst | 225 tight timing-based admission control for up to 1024 flows (identified by a
|
/linux-6.12.1/Documentation/networking/device_drivers/ethernet/intel/ |
D | ixgbe.rst | 317 - Enables tight control on routing a flow in the platform.
|
D | i40e.rst | 128 - Enables tight control on routing a flow in the platform.
|
D | ice.rst | 195 - Enables tight control on routing a flow in the platform
|
/linux-6.12.1/Documentation/RCU/Design/Expedited-Grace-Periods/ |
D | Expedited-Grace-Periods.rst | 505 tight synchronization between expedited grace periods and CPU-hotplug
|
/linux-6.12.1/Documentation/userspace-api/media/v4l/ |
D | ext-ctrls-codec.rst | 1750 #. For tight CBR, this field must be small (ex. 2 ~ 10). For 1830 will meet tight bandwidth constraints. Applicable to encoders.
|
/linux-6.12.1/kernel/trace/ |
D | Kconfig | 893 As it is a tight loop, it benchmarks as hot cache. That's fine because
|
/linux-6.12.1/Documentation/RCU/Design/Requirements/ |
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-6.12.1/Documentation/admin-guide/pm/ |
D | cpuidle.rst | 629 more or less "lightweight" sequence of instructions in a tight loop. [Note
|
/linux-6.12.1/Documentation/filesystems/xfs/ |
D | xfs-online-fsck-design.rst | 1653 chain, but it is theoretically possible if space is very tight. 2386 If space is tight, the loading factor will be set to maxrecs to try to avoid
|