Home
last modified time | relevance | path

Searched full:much (Results 1 – 25 of 429) sorted by relevance

12345678910>>...18

/Documentation/filesystems/bcachefs/
Derrorcodes.rst10 This gives us much better error messages and makes debugging much easier. Any
29 where the error was generated; good names for error codes mean much more
DCodingStyle.rst56 invariants with runtime checks - much like the way people working in
78 make your error messages much easier to write (therefore they will actually
79 exist) and much more informative. And they can be used from sysfs/debugfs, as
135 Nobody writes all perfect code that all gets shipped, and you'll be much more
150 much less risk of wasted effort if the feature you were going for doesn't work
/Documentation/arch/x86/
Dorc-unwinder.rst12 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
/Documentation/
Dsubsystem-apis.rst8 from the point of view of a kernel developer. Much of the information here
66 **Fixme**: much more organizational work is needed here.
/Documentation/ABI/testing/
Dsysfs-kernel-dmaheap6 The total_pools_kb file is read-only and specifies how much
/Documentation/arch/powerpc/
Dkasan.txt48 this at run-time based on how much physical memory we have, but this requires
54 requires knowing how much contiguous physical memory a system has _at compile
/Documentation/ABI/stable/
Dsyscalls3 This interface matches much of the POSIX interface and is based
/Documentation/scheduler/
Dsched-nice-design.rst9 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
Dsched-design-CFS.rst69 side of the tree as much as possible.
115 The CFS scheduler has a much stronger handling of nice levels and SCHED_BATCH
116 than the previous vanilla scheduler: both types of workloads are isolated much
157 without the core code assuming too much about them.
/Documentation/misc-devices/
Dapds990x.rst26 might vary quite much depending the spectrum of the light source.
68 to saturate much before that. Real max value varies depending
/Documentation/process/
Dbotching-up-ioctls.rst14 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
Ddevelopment-process.rst11 there is some technical material here, this is very much a process-oriented
/Documentation/ABI/removed/
Draw13948 of abstraction that required userspace clients to duplicate much
/Documentation/admin-guide/pm/
Dstrategies.rst42 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
/Documentation/userspace-api/media/v4l/
Dpixfmt-bayer.rst12 The raw Bayer formats are used by image sensors before much if any processing is
/Documentation/admin-guide/namespaces/
Dresource-control.rst13 that userspace configure memory control groups to limit how much
/Documentation/arch/arm/samsung/
Dgpio.rst15 The gpio implementation uses gpiolib as much as possible, only providing
/Documentation/driver-api/surface_aggregator/
Doverview.rst17 Not much is currently known about SAM on 4th generation devices (Surface Pro
32 While features have not changed much on a coarse level since the 5th
/Documentation/driver-api/driver-model/
Ddevres.rst15 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
/Documentation/security/tpm/
Dtpm_ftpm_tee.rst19 implemented in firmware. The driver itself doesn't contain much logic and is
/Documentation/devicetree/bindings/i3c/
Dmipi-i3c-hci.yaml24 isn't much to describe here (yet).
/Documentation/devicetree/bindings/regulator/
Drichtek,rt4831-regulator.yaml21 voltage needed for DSVP and DSVN. Too much voltage gap could improve the
/Documentation/scsi/
Dsym53c500_cs.rst22 other products using this chip, but I've never laid eyes (much less hands)
/Documentation/userspace-api/
Dindex.rst7 While much of the kernel's user-space API is documented elsewhere
/Documentation/devicetree/bindings/input/touchscreen/
Dtsc2007.txt20 - ti,poll-period: how much time to wait (in milliseconds) before reading again the

12345678910>>...18