Searched full:much (Results 1 – 25 of 2344) sorted by relevance
12345678910>>...94
| /kernel/linux/linux-5.10/drivers/media/pci/bt8xx/ |
| D | bttv-audio-hook.c | 60 /* Not much to do here */ in gvbctv3pci_audio()
162 /* Not much to do here */ in avermedia_tvphone_audio()
193 /* Not much to do here */ in avermedia_tv_stereo_audio()
231 /* Not much to do here */ in lt9415_audio()
264 /* Not much to do here */ in terratv_audio()
297 /* Not much to do here */ in winfast2000_audio()
344 /* Not much to do here */ in pvbt878p9b_audio()
385 /* Not much to do here */ in fv2000s_audio()
421 /* Not much to do here */ in windvr_audio()
458 /* Not much to do here */ in adtvk503_audio()
|
| /kernel/linux/linux-5.10/Documentation/x86/ |
| D | orc-unwinder.rst | 12 format of the ORC data is much simpler than DWARF, which in turn allows
13 the ORC unwinder to be much simpler and faster.
63 ORC debuginfo's advantage over DWARF itself is that it's much simpler.
66 much simpler, meaning fewer bugs, which is especially important for
69 The simpler debuginfo format also enables the unwinder to be much faster
114 annotations are needed than what DWARF would need, so they're much more
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | timex.h | 90 * SHIFT_PLL is used as a dampening factor to define how much we
93 * much of the current value in time_offset we correct for each
100 * However this seems to increase convergence time much too long.
114 * SHIFT_FLL is used as a dampening factor to define how much we
|
| D | stringhash.h | 18 * malicious inputs; much slower hash functions are required for that.
62 * this computes a different hash function much faster.
|
| D | nfs_iostat.h | 48 * traffic. NORMAL + DIRECT shows how much data is going through
50 * without much NORMAL or DIRECT traffic shows that applications
|
| D | seq_buf.h | 57 * How much buffer is left on the seq_buf?
68 /* How much buffer was written? */
|
| D | trace_seq.h | 61 * trace_seq_has_overflowed - return true if the trace_seq took too much
64 * Returns true if too much data was added to the trace_seq and it is
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | botching-up-ioctls.rst | 14 actually only used once interfaces. But the clear downside is that there's much
110 paths pretty much for free for graphics drivers. Also, be consistent with
160 an asynchronous event on a pollable file descriptor. It fits much better
208 it's much quicker to push a driver-private interface than engaging in
214 * Consider other interfaces than ioctls. A sysfs attribute is much better for
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/ |
| D | floppy.h | 42 * driver otherwise. It doesn't matter much for performance anyway, as most
47 * Actually this needs to be a bit more complicated since the so much different
|
| /kernel/linux/linux-5.10/Documentation/scheduler/ |
| D | sched-nice-design.rst | 9 pestered us to make nice +19 tasks use up much less CPU time.
17 much stronger than they were before in 2.4 (and people were happy about
39 So that if someone wanted to really renice tasks, +19 would give a much
|
| D | sched-design-CFS.rst | 65 side of the tree as much as possible.
108 The CFS scheduler has a much stronger handling of nice levels and SCHED_BATCH
109 than the previous vanilla scheduler: both types of workloads are isolated much
150 without the core code assuming too much about them.
|
| /kernel/linux/linux-5.10/Documentation/ |
| D | index.rst | 15 documentation, like the kernel itself, is very much a work in progress;
72 merged much easier.
91 from the point of view of a kernel developer. Much of the information here
|
| /kernel/linux/linux-5.10/net/batman-adv/ |
| D | bitarray.c | 60 /* sequence number is much newer, probably missed a lot of packets */ in batadv_bit_get_packet()
72 /* received a much older packet. The other host either restarted in batadv_bit_get_packet()
|
| /kernel/linux/linux-5.10/arch/arm/include/asm/ |
| D | kgdb.h | 34 * make our lives much much simpler. :)
|
| /kernel/linux/linux-5.10/Documentation/misc-devices/ |
| D | apds990x.rst | 26 might vary quite much depending the spectrum of the light source.
68 to saturate much before that. Real max value varies depending
|
| /kernel/linux/linux-5.10/Documentation/driver-api/driver-model/ |
| D | devres.rst | 15 5. Overhead : How much do we have to pay for this?
35 For one reason or another, low level drivers don't receive as much
38 Init failure path is worse because it's much less travelled while
102 driver can have much simpler init and exit code. Init path basically
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | README.rst | 50 system: there are much better sources available.
192 values to 'y' as much as possible.
196 values to 'm' as much as possible.
199 values to 'n' as much as possible.
374 me or anybody else very much: it will depend on your particular
400 kernel image or similar), telling me as much about your setup as
|
| /kernel/linux/linux-5.10/drivers/tty/ |
| D | ehv_bytechan.c | 355 /* Find out how much data needs to be read, and then ask the TTY layer in ehv_bc_tty_rx_isr()
356 * if it can handle that much. We want to ensure that every byte we in ehv_bc_tty_rx_isr()
404 * This function, which can be called in interrupt context, dequeues as much
460 * the data first in a circular buffer, and then dequeue as much of that data
465 * layer how much data it can safely send to us. We guarantee that
467 * too much data.
536 * how much write room the driver can guarantee will be sent OR BUFFERED. This
599 * If we could ask the hypervisor how much data is still in the TX buffer, or
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| D | strategies.rst | 42 then it takes much less time and effort to start executing user space code than
45 typically the system can spend much more time in a sleep state than it can be
|
| /kernel/linux/linux-5.10/fs/jffs2/ |
| D | compr_rtime.c | 69 /* Tell the caller how much we managed to compress, and how much space it took */ in jffs2_rtime_compress()
|
| /kernel/linux/linux-5.10/drivers/block/drbd/ |
| D | drbd_vli.h | 20 * the bitmap transfer time can take much too long,
37 * integers would be much worse than plaintext.
48 * We don't care too much about "excellent" compression ratio for large
50 * or 1000 is not that much of an issue.
51 * We do not want to waste too much on short runlengths in the "noisy"
|
| /kernel/linux/linux-5.10/arch/alpha/lib/ |
| D | ev67-strchr.S | 9 * Much of the information about 21264 scheduling/coding comes from:
65 * data to be loaded. Not much can be done about it unless it's
|
| /kernel/linux/linux-5.10/fs/reiserfs/ |
| D | README | 117 that he was shown much generosity just makes it more painful.
135 Igor Zagorovsky is writing much of the new item handler and extent code
159 than the ones just named. SuSE has helped in much more than just
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/ |
| D | nvidia,tegra20-i2c.txt | 20 very much similar to Tegra20 I2C controller with additional feature:
27 very much similar to Tegra30 I2C controller with some hardware
|
| /kernel/linux/linux-5.10/arch/sparc/include/asm/ |
| D | switch_to_32.h | 47 /* Much care has gone into this code, do not touch it.
55 * Hey Dave, that do not touch sign is too much of an incentive
|
12345678910>>...94