Home
last modified time | relevance | path

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

/linux-6.15/fs/erofs/
H A Dzdata.c982 bool tight, excl; in z_erofs_scan_folio() local
985 tight = (bs == PAGE_SIZE); in z_erofs_scan_folio()
1005 tight = false; in z_erofs_scan_folio()
1014 tight = false; in z_erofs_scan_folio()
1031 tight &= (f->mode >= Z_EROFS_PCLUSTER_FOLLOWED); in z_erofs_scan_folio()
1034 excl = (split <= 1) || tight; in z_erofs_scan_folio()
1060 tight = (bs == PAGE_SIZE); in z_erofs_scan_folio()
/linux-6.15/drivers/iio/trigger/
H A DKconfig54 Uses a tight loop in a kthread. Will only work with lower half only
/linux-6.15/Documentation/filesystems/
H A Dcramfs.rst66 handy for tiny embedded systems with very tight memory constraints.
H A Dmultigrain-ts.rst96 This ensures tight cache coherency for use-cases like NFS, without sacrificing
H A Daffs.rst229 is also true when space gets tight.
/linux-6.15/Documentation/block/
H A Dbfq-iosched.rst132 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.15/Documentation/fb/
H A Dudlfb.rst36 tight relative to the functionality it provides.
/linux-6.15/Documentation/admin-guide/
H A Drtc.rst75 typical 486-33 running a tight read loop on /dev/rtc will start to suffer
H A Dcgroup-v2.rst1211 While not completely water-tight, all major memory usages by a given
3306 anonymous memory in a tight loop - and an admin can not assume full
H A Dkernel-parameters.txt5573 period to do tight-loop forward-progress testing.
5581 need_resched() during tight-loop forward-progress
/linux-6.15/Documentation/timers/
H A Dhrtimers.rst25 code is very good and tight code, there's zero problems with it in its
/linux-6.15/Documentation/driver-api/usb/
H A DURB.rst142 allocation, such as whether the lower levels may block when memory is tight.
/linux-6.15/Documentation/sound/designs/
H A Dcompress-offload.rst290 API. Support for dynamic bit-rate changes would require a tight
/linux-6.15/Documentation/security/
H A Dself-protection.rst45 the kernel needs to protect its memory with a tight set of permissions.
/linux-6.15/Documentation/power/
H A Denergy-model.rst175 cpufreq_register_em_with_opp(). It implements a power model which is tight to
/linux-6.15/Documentation/networking/dsa/
H A Dsja1105.rst225 tight timing-based admission control for up to 1024 flows (identified by a
/linux-6.15/Documentation/networking/device_drivers/ethernet/intel/
H A Dixgbe.rst317 - Enables tight control on routing a flow in the platform.
H A Di40e.rst128 - Enables tight control on routing a flow in the platform.
H A Dice.rst226 - Enables tight control on routing a flow in the platform
/linux-6.15/Documentation/RCU/Design/Expedited-Grace-Periods/
H A DExpedited-Grace-Periods.rst505 tight synchronization between expedited grace periods and CPU-hotplug
/linux-6.15/Documentation/userspace-api/media/v4l/
H A Dext-ctrls-codec.rst1750 #. For tight CBR, this field must be small (ex. 2 ~ 10). For
1830 will meet tight bandwidth constraints. Applicable to encoders.
/linux-6.15/Documentation/RCU/Design/Requirements/
H A DRequirements.rst1425 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.15/kernel/trace/
H A DKconfig924 As it is a tight loop, it benchmarks as hot cache. That's fine because
/linux-6.15/Documentation/admin-guide/pm/
H A Dcpuidle.rst624 more or less "lightweight" sequence of instructions in a tight loop. [Note
/linux-6.15/Documentation/filesystems/xfs/
H A Dxfs-online-fsck-design.rst1653 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