Home
last modified time | relevance | path

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

12345678910>>...72

/Linux-v6.6/Documentation/ABI/testing/
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.
Dsysfs-platform-hidma-mgmt64 Choosing a higher number gives better performance but
85 Choosing a higher number gives better performance but
/Linux-v6.6/fs/ntfs/
Dtypes.h27 * and VCN, to allow for type checking and better code readability.
36 * values. We define our own type LSN, to allow for type checking and better
44 * We define our own type USN, to allow for type checking and better code
/Linux-v6.6/Documentation/hwmon/
Dlm90.rst499 * Better external channel accuracy
528 * Better local resolution (10 bit)
532 * Better local resolution
536 * Better local resolution
540 * Better local resolution
547 * Better local resolution
551 * Better local resolution
561 * Better local resolution
577 * Better local resolution
/Linux-v6.6/arch/alpha/include/asm/
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-v6.6/Documentation/admin-guide/cifs/
Dtodo.rst38 handle caching leases) and better using reference counters on file
49 (requires minor protocol extension) to enable better support for SELINUX
56 exists. Also better integration with winbind for resolving SID owners
119 cifs/smb3 better
/Linux-v6.6/arch/x86/lib/
Dmemset_64.S13 * string to get better performance than the original function. The code is
24 * from the compiler for better calling conventions.
29 * which the compiler could/should do much better anyway.
/Linux-v6.6/tools/arch/x86/lib/
Dmemset_64.S13 * string to get better performance than the original function. The code is
24 * from the compiler for better calling conventions.
29 * which the compiler could/should do much better anyway.
/Linux-v6.6/drivers/parport/
DTODO-parport7 2. A better lp.c:
18 4. A better PLIP (make use of bidirectional/ECP/EPP ports).
/Linux-v6.6/Documentation/process/
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
D7.AdvancedTopics.rst20 BitKeeper. For better or for worse, the kernel project has settled on git
155 reviewing patches. It is certainly true that there is no better way to
167 get released in this path?" will always work better than stating "the
177 All types of review, if they lead to better code going into the kernel, are
/Linux-v6.6/tools/testing/selftests/tc-testing/
DTODO.txt9 need to better handle problems in pre- and post-suite.
16 - A better implementation of the "hooks". Currently, every plugin
/Linux-v6.6/drivers/mfd/
Drk8xx-i2c.c29 * we don't use that feature. It's better to cache. in rk808_is_volatile_reg()
31 * bits are cleared in case when we shutoff anyway, but better safe. in rk808_is_volatile_reg()
57 * we don't use that feature. It's better to cache. in rk817_is_volatile_reg()
/Linux-v6.6/drivers/gpu/drm/i915/gem/
Di915_gemfs.c22 * mount flags that better match our usecase. in i915_gemfs_init()
24 * One example, although it is probably better with a per-file in i915_gemfs_init()
/Linux-v6.6/arch/arm64/kvm/hyp/nvhe/
Dtlb.c90 * We could do so much better if we had the VA as well. in __kvm_tlb_flush_vmid_ipa()
121 * the host is running at EL1. As above, we could do better if in __kvm_tlb_flush_vmid_ipa()
142 * We could do so much better if we had the VA as well. in __kvm_tlb_flush_vmid_ipa_nsh()
173 * the host is running at EL1. As above, we could do better if in __kvm_tlb_flush_vmid_ipa_nsh()
/Linux-v6.6/Documentation/networking/device_drivers/can/freescale/
Dflexcan.rst25 performs better under high system load situations.
47 This mode activates the "RX mailbox mode" for better performance, on
/Linux-v6.6/fs/verity/
DKconfig32 data each time it is paged back in, which provides better
48 IMA appraisal) can be much better. For details about the
/Linux-v6.6/Documentation/ABI/obsolete/
Dsysfs-bus-iio8 so, it is better to use, instead:
20 so, it is better to use, instead:
169 so, it is better to use, instead:
184 so, it is better to use, instead:
/Linux-v6.6/Documentation/filesystems/ext4/
Dallocators.rst6 ext4 recognizes (better than ext3, anyway) that data locality is
30 is that the filesystem can make better location decisions.
/Linux-v6.6/Documentation/arch/arm/
Dmem_alignment.rst15 are better to use the macros provided by include/asm/unaligned.h. The
17 a high performance cost. It better be rare.
/Linux-v6.6/drivers/net/wireless/realtek/rtlwifi/rtl8192se/
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-v6.6/arch/arc/include/uapi/asm/
Dswab.h13 * -Better htonl implementation (5 instead of 9 ALU instructions)
64 * Joern suggested a better "C" algorithm which is great since
/Linux-v6.6/fs/erofs/
DKconfig95 gives better compression ratios than the LZ4 algorithm, at the
109 containing DEFLATE compressed data. It gives better compression
/Linux-v6.6/Documentation/networking/
Dnet_dim.rst50 A step would result as "better" if bandwidth increases and as "worse" if
52 compared in a similar fashion - increase == "better" and decrease == "worse".
56 considered "better". Step #2 has an optimization for avoiding false results: it
/Linux-v6.6/drivers/infiniband/hw/qib/
Dqib_intr.c96 * states, or if it transitions from any of the up (INIT or better) in qib_handle_e_ibstatuschanged()
220 /* separate routine, for better optimization of qib_intr() */ in qib_bad_intrstatus()
224 * having a better chance of debugging the problem. in qib_bad_intrstatus()

12345678910>>...72