Searched refs:tight (Results 1 – 10 of 10) sorted by relevance
/linux-4.1.27/drivers/gpu/drm/msm/mdp/ |
D | mdp_format.c | 74 #define FMT(name, a, r, g, b, e0, e1, e2, e3, alpha, tight, c, cnt, fp, cs) { \ argument 82 .unpack_tight = tight, \
|
/linux-4.1.27/Documentation/locking/ |
D | mutex-design.txt | 49 the unlocking fastpath is equally tight:
|
/linux-4.1.27/Documentation/fb/ |
D | udlfb.txt | 36 tight relative to the functionality it provides.
|
/linux-4.1.27/Documentation/filesystems/ |
D | affs.txt | 201 is also true when space gets tight.
|
/linux-4.1.27/Documentation/timers/ |
D | hrtimers.txt | 25 code is very good and tight code, there's zero problems with it in its
|
/linux-4.1.27/Documentation/usb/ |
D | URB.txt | 127 such as whether the lower levels may block when memory is tight.
|
/linux-4.1.27/Documentation/sound/alsa/ |
D | compress_offload.txt | 197 API. Support for dynamic bit-rate changes would require a tight
|
/linux-4.1.27/Documentation/ |
D | rtc.txt | 75 typical 486-33 running a tight read loop on /dev/rtc will start to suffer
|
/linux-4.1.27/Documentation/networking/ |
D | ixgbe.txt | 125 different queues. Enables tight control on routing a flow in the platform.
|
/linux-4.1.27/kernel/trace/ |
D | Kconfig | 556 As it is a tight loop, it benchmarks as hot cache. That's fine because
|