Searched full:very (Results 1 – 25 of 2635) sorted by relevance
12345678910>>...106
| /kernel/linux/linux-5.10/net/mac80211/ |
| D | Kconfig | 170 very verbose OCB debugging messages. It should not
181 very verbose IBSS debugging messages. It should not
191 Selecting this option causes mac80211 to print out very
204 Selecting this option causes mac80211 to print out very
217 Selecting this option causes mac80211 to print out very
230 Selecting this option causes mac80211 to print out very
243 Selecting this option causes mac80211 to print out very verbose mesh
254 Selecting this option causes mac80211 to print out very verbose mesh
265 Selecting this option causes mac80211 to print out very verbose mesh
275 Selecting this option causes mac80211 to print out very
[all …]
|
| /kernel/linux/linux-5.10/drivers/misc/echo/ |
| D | echo.h | 40 things like modem line equalisers and line echo cancellers. There it works very
42 very poorly for things like speech echo cancellation, where the signal level
53 the NLMS algorithm works very well. However, speech has more low frequency than
56 final residual signal is not heavily biased towards high frequencies. A very
70 noise like, such as voice) the adaption works very well. If the adaption is
94 energy is that we must do this very quickly. Given a reasonably long sample of
99 needed which produces a fairly accurate result from a very short burst of far
|
| /kernel/linux/linux-5.10/Documentation/virt/ |
| D | paravirt_ops.rst | 25 known that the overhead of indirect call isn't very important.
30 very important.
35 them are very performance critical.
|
| /kernel/linux/linux-5.10/Documentation/accounting/ |
| D | cgroupstats.rst | 11 and attributes specific to cgroups. It should be very easy to
16 statistics on interesting events), should be very easy to add. Currently
25 To extract cgroup statistics a utility very similar to getdelays.c
|
| /kernel/linux/linux-5.10/drivers/hid/ |
| D | hid-holtekff.c | 43 * 1: very strong rumble
45 * 3: very strong rumble
51 * 9: very strong rumble
53 * b: very strong periodic rumble, very short intervals
|
| /kernel/linux/linux-5.10/tools/perf/arch/s390/util/ |
| D | machine.c | 38 /* On s390 kernel text segment start is located at very low memory addresses,
39 * for example 0x10000. Modules are located at very high memory addresses,
41 * and beginning of first module's text segment is very big.
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | stable-api-nonsense.rst | 19 the syscall interface. That interface is **very** stable over time, and
69 very important.
146 Security issues are also very important for Linux. When a
147 security issue is found, it is fixed in a very short amount of time. A
178 time, with very little effort on your part.
180 The very good side effects of having your driver in the main kernel tree
|
| /kernel/linux/linux-5.10/drivers/mtd/maps/ |
| D | Kconfig | 191 mtd1 allows you to reprogram your BIOS. BE VERY CAREFUL.
231 BE VERY CAREFUL.
240 BE VERY CAREFUL.
249 BE VERY CAREFUL.
258 BE VERY CAREFUL.
267 BE VERY CAREFUL.
294 BE VERY CAREFUL.
|
| /kernel/linux/linux-5.10/Documentation/vm/ |
| D | zsmalloc.rst | 9 never attempts higher order page allocation which is very likely to
11 (0-order) pages, it would suffer from very high fragmentation --
32 is very small. So, before using the allocating memory, the object has to
|
| /kernel/linux/linux-5.10/Documentation/ia64/ |
| D | efirtc.rst | 26 The original ideas was to provide a very simple driver to get access to,
32 the CMOS clock, we decided to expose an API that was very similar to the one
41 expose this new way of representing time. Instead we use something very
107 i.e. reboot. This is very different from the alarm provided by the legacy
|
| /kernel/linux/linux-5.10/tools/power/cpupower/man/ |
| D | cpupower-idle-info.1 | 26 statistics when it enters or leaves an idle state, therefore on a very idle or
27 a very busy system, these statistics may not be accurate. They still provide a
50 very soon and entering any real hardware idle state may result in a slight
|
| /kernel/linux/linux-5.10/Documentation/fb/ |
| D | udlfb.rst | 18 does not require any acks - the effect is very low latency that
23 setting is very flexible - able to set nearly arbitrary modes from any timing.
121 Enabled by default. Only disable on very low memory systems.
157 roll over very quickly. To get reliable results, design
158 performance tests to start and finish in a very short
|
| /kernel/linux/linux-5.10/drivers/staging/vc04_services/interface/ |
| D | TODO | 51 kthreads, userspace, limitations) could be very helpful for reviewers.
55 There is a heavy use of memory barriers in this driver, it would be very
68 indentation deep making it very unpleasant to read. This is specially relevant
|
| /kernel/linux/linux-5.10/arch/powerpc/include/asm/ |
| D | perf_event_fsl_emb.h | 31 * This isn't a very flexible method of expressing constraints,
32 * but it's very simple and is adequate for existing chips.
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | percpu-rw-semaphore.rst | 13 Locking for reading is very fast, it uses RCU and it avoids any atomic
15 writing is very expensive, it calls synchronize_rcu() that can take
|
| D | robust-futexes.rst | 28 method makes futexes very lightweight and scalable.
73 This is very much noticeable even for normal process sys_exit_group()
128 over every vma (!), which the VM-based method has to do. Only a very
134 need any extra per-lock syscalls. Robust mutexes thus become a very
180 List registration is very fast: the pointer is simply stored in
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | edd.h | 11 * very similar to D1484 Revision 3 http://www.t13.org/docs2002/d1484r3.pdf
19 * is very sensitive to the size of these structures.
|
| /kernel/linux/linux-5.10/Documentation/power/regulator/ |
| D | design.rst | 11 - Errors in regulator configuration can have very serious consequences
37 very easy to handle and so that consumers will work with shared
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/light/ |
| D | cm3605.txt | 7 This ALS and proximity sensor was one of the very first deployed in mobile
8 handsets, notably it is used in the very first Nexus One Android phone from
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | romfs.rst | 9 modules linked at boot time. Using this filesystem, you get a very
30 However, the main purpose of romfs is to have a very small kernel,
50 structure is very simple. Every accessible structure begins on 16
88 reliable, it does not require any tables, and it is very simple.
171 - The file system is read only, so it can be very small, but in case
|
| /kernel/linux/linux-5.10/arch/arm/mach-mvebu/ |
| D | coherency_ll.S | 84 * calls. This function is used very early in the secondary
109 * calls. This function is used very early in the secondary
136 * calls. This function is used very early in the secondary
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | zero.rst | 11 One very interesting use of dm-zero is for creating "sparse" devices in
17 device is deactivated. This can be very useful for testing device and
|
| /kernel/linux/linux-5.10/arch/x86/ |
| D | Kconfig.debug | 27 This is useful for kernel debugging when your machine crashes very
40 This is useful for kernel debugging when your machine crashes very
54 machine crashes very early before the regular console code is
63 crashes or need a very simple printk logging facility.
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | adm1021.rst | 101 The chips supported by this driver are very similar. The Maxim MAX1617 is
102 the oldest; it has the problem that it is not very well detectable. The
108 code. This can help us pinpoint problems; it is not very useful
|
| /kernel/linux/linux-5.10/tools/objtool/arch/x86/ |
| D | special.c | 31 * feature path which is a "very very small percentage of in arch_handle_alternative()
47 * encounters a branch instruction at the very beginning of the in arch_support_alt_relocation()
|
12345678910>>...106