Home
last modified time | relevance | path

Searched full:better (Results 1 – 25 of 1486) sorted by relevance

12345678910>>...60

/linux/Documentation/admin-guide/cifs/
H A Dtodo.rst23 b) Better optimized compounding and error handling for sparse file support,
39 handle caching leases) and better using reference counters on file
50 (requires minor protocol extension) to enable better support for SELINUX
57 exists. Also better integration with winbind for resolving SID owners
101 y) Improved tracing, more eBPF trace points, better scripts for performance
117 cifs/smb3 better
/linux/Documentation/ABI/testing/
H A Dsysfs-bus-iio-bno05557 the number, the better the calibration status.
65 the number, the better the calibration status.
73 the number, the better the calibration status.
81 the number, the better the calibration status.
H A Dsysfs-platform-hidma-mgmt64 Choosing a higher number gives better performance but
85 Choosing a higher number gives better performance but
/linux/tools/sched_ext/
H A DKconfig20 # (i.e., avoiding lock holder preemption) for better system-wide progress.
29 # Enable extra scheduling features (for a better code coverage while testing
36 # Enable fully preemptible kernel for a better test coverage of the schedulers
/linux/arch/alpha/include/asm/
H A Dwrperfmon.h17 /* Following commands are on EV5 and better CPUs */
20 /* Following command are on EV6 and better CPUs */
22 /* Following command are on EV67 and better CPUs */
/linux/tools/arch/x86/lib/
H A Dmemset_64.S14 * string to get better performance than the original function. The code is
25 * from the compiler for better calling conventions.
30 * which the compiler could/should do much better anyway.
/linux/Documentation/process/
H A Dmanagement-style.rst45 manage had better know the details better than you, so if they come to
49 (Corollary:if the people you manage don't know the details better than
118 Remember: they'd better know more about the details than you do, and
125 clear which approach is better, they'll eventually figure it out. The
188 knowledge that we're better than the average person (let's face it,
251 We all think we're better than anybody else, which means that when
H A Dbotching-up-ioctls.rst160 an asynchronous event on a pollable file descriptor. It fits much better
214 * Consider other interfaces than ioctls. A sysfs attribute is much better for
218 disclaimer of not having a stable ABI would be better.
/linux/fs/erofs/
H A DKconfig134 gives better compression ratios than the default LZ4 format, at the
144 containing DEFLATE compressed data. It gives better compression
155 containing Zstandard compressed data. It gives better compression
166 EROFS file systems containing compressed data. It gives better
/linux/drivers/parport/
H A DTODO-parport7 2. A better lp.c:
18 4. A better PLIP (make use of bidirectional/ECP/EPP ports).
/linux/scripts/
H A Dxz_wrap.sh66 "for better compression" >&2
112 "for better compression" >&2
151 # Use single-threaded mode because it compresses a little better
/linux/tools/testing/selftests/tc-testing/
H A DTODO.txt9 need to better handle problems in pre- and post-suite.
16 - A better implementation of the "hooks". Currently, every plugin
/linux/fs/verity/
H A DKconfig29 data each time it is paged back in, which provides better
45 IMA appraisal) can be much better. For details about the
/linux/Documentation/ABI/obsolete/
H A Dsysfs-bus-iio8 so, it is better to use, instead:
20 so, it is better to use, instead:
157 so, it is better to use, instead:
172 so, it is better to use, instead:
/linux/Documentation/networking/device_drivers/can/freescale/
H A Dflexcan.rst25 performs better under high system load situations.
47 This mode activates the "RX mailbox mode" for better performance, on
/linux/lib/crc/x86/
H A Dcrc-pclmul-template.h49 * has touched, which could result in a larger cutoff being better. Indeed, a
50 * larger cutoff is usually better for a *single* message. However, the
/linux/Documentation/filesystems/ext4/
H A Dallocators.rst6 ext4 recognizes (better than ext3, anyway) that data locality is
30 is that the filesystem can make better location decisions.
/linux/drivers/net/wireless/realtek/rtlwifi/rtl8192se/
H A Drf.c165 /* Realtek better performance increase power diff in _rtl92s_get_txpower_writeval_byregulatory()
173 "RTK better performance, writeval = 0x%x\n", writeval); in _rtl92s_get_txpower_writeval_byregulatory()
208 /* Better regulatory don't increase any power diff */ in _rtl92s_get_txpower_writeval_byregulatory()
211 "Better regulatory, writeval = 0x%x\n", writeval); in _rtl92s_get_txpower_writeval_byregulatory()
272 "RTK better performance, writeval = 0x%x\n", writeval); in _rtl92s_get_txpower_writeval_byregulatory()
/linux/Documentation/arch/arm/
H A Dmem_alignment.rst15 are better to use the macros provided by include/linux/unaligned.h. The
17 a high performance cost. It better be rare.
/linux/arch/x86/lib/
H A Dcsum-partial_64.c5 * This file contains network checksum routines that are better done
48 /* Do two 40-byte chunks in parallel to get better ILP */ in csum_partial()
/linux/drivers/net/ethernet/amd/
H A DKconfig83 DEPCA series. (This chipset is better known via the NE2100 cards.)
132 cards are based on the AMD LANCE chipset, which is better known
/linux/Documentation/scheduler/
H A Dsched-util-clamp.rst17 scheduler to make a better decision. And when schedutil cpufreq governor is
39 the uclamp values as performance points rather than utilization is a better
93 The overall visible effect goes beyond better perceived user
94 experience/performance and stretches to help achieve a better overall
528 better decision about task placement and frequency selection.
532 dynamically monitor and adjust. Ultimately this will allow for a better user
533 experience at a better perf/watt.
/linux/include/linux/crush/
H A Dcrush.h110 * straw O(n) better better
263 * mappings line up a bit better with previous mappings. */
/linux/Documentation/driver-api/
H A Dioctl.rst61 A better approach is to add a new ioctl command with a new number. The
188 but some properties of them are implementation-defined, so it is better
237 * System calls are a better choice for a system-wide feature that
/linux/Documentation/usb/
H A Dehci.rst186 It's expected that newer implementations will better this, throwing
209 than the I/O. If that same loop used 16 KB chunks, it'd be better; a
213 I/O be efficient, it's better to just queue up several (bulk) requests

12345678910>>...60