Searched full:very (Results 1 – 25 of 556) sorted by relevance
12345678910>>...23
| /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.
|
| /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
|
| /Documentation/devicetree/bindings/i2c/ |
| D | nvidia,tegra20-i2c.yaml | 28 Tegra30 has 5 generic I2C controller. This controller is very much
39 Tegra114 has 5 generic I2C controllers. This controller is very much
52 Tegra124 has 6 generic I2C controllers. These controllers are very
57 Tegra210 has 6 generic I2C controllers. These controllers are very
73 (always-on) partition of the SoC. All of these controllers are very
78 (always-on) partition of the SoC. All of these controllers are very
|
| /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
|
| /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
|
| /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
|
| /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
|
| D | management-style.rst | 12 Management style is very personal and much harder to quantify than
39 manager must be to make it. That's very deep and obvious, but it's not
80 back-tracking is very easy: just tell everybody that you were an
91 wrong is sometimes very hard indeed.
104 your mind, and make people very **aware** of that. And it's much easier
159 The problem with #1 is that it's very easy to do, since you can say
|
| D | development-process.rst | 11 there is some technical material here, this is very much a process-oriented
|
| /Documentation/hwmon/ |
| D | lm70.rst | 55 The LM74 and TMP121/TMP122/TMP123/TMP124 are very similar; main difference is
63 The LM71 is also very similar; main difference is 14-bit temperature
|
| /Documentation/devicetree/bindings/iio/light/ |
| D | capella,cm3605.yaml | 18 This ALS and proximity sensor was one of the very first deployed in mobile
19 handsets, notably it is used in the very first Nexus One Android phone from
|
| D | rohm,bu27034anuc.yaml | 14 capable of detecting a very wide range of illuminance. Typical application
|
| /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.
128 Enabled by default. Only disable on very low memory systems.
164 roll over very quickly. To get reliable results, design
165 performance tests to start and finish in a very short
|
| /Documentation/userspace-api/media/v4l/ |
| D | hsv-formats.rst | 12 and the distance to the center is the SATURATION. This is a very
|
| D | ext-ctrls-rf-tuner.rst | 59 The RF amplifier is the very first amplifier on the receiver signal
68 signal path. It is located very close to tuner antenna input. Used
|
| D | colorspaces.rst | 9 'Color' is a very complex concept and depends on physics, chemistry and
57 define a color without the luminance component Y. It is very confusing
150 mix of different standards also led to very confusing naming conventions
163 article is also very useful.
|
| D | selections-common.rst | 9 :ref:`V4L2 subdev selection APIs <v4l2-subdev-selections>` are very
|
| /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
|
| D | ubifs.rst | 38 It should be quite obvious why UBIFS is very different to traditional
45 is very similar to MTD devices - they still consist of large eraseblocks,
50 very different and incompatible to JFFS2. The following are the main
|
| /Documentation/networking/ |
| D | ipvlan.rst | 12 This is conceptually very similar to the macvlan driver with one major
88 This is very similar to the L3 mode except that iptables (conn-tracking)
123 These two devices are very similar in many regards and the specific use
124 case could very well define which device to choose. if one of the following
|
| /Documentation/driver-api/media/drivers/ |
| D | dvb-usb.rst | 116 - refactoring completed, now everything is very delightful
302 frequency simply does not work very well. This applies to all USB1.1
313 Patches, comments and suggestions are very very welcome.
357 hardware and listening to my problems very patiently.
|
| D | pvrusb2.rst | 26 This driver has a strong separation of layers. They are very
160 pvrusb2-io.[ch] - This module implements a very low level ring of
162 device. This module is *very* low level. It only operates the
201 (and at the moment the driver has very little that needs to be
|
| /Documentation/networking/mac80211_hwsim/ |
| D | mac80211_hwsim.rst | 23 hostapd and wpa_supplicant) in a way that matches very closely with
38 configuration of both very simply setups (e.g., just a single access
|
| /Documentation/devicetree/bindings/iio/proximity/ |
| D | semtech,sx9310.yaml | 69 - very-coarse
74 - very-fine
|
12345678910>>...23