Searched full:important (Results 1 – 25 of 1410) sorted by relevance
12345678910>>...57
| /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.
|
| /kernel/linux/linux-5.10/arch/mips/kernel/ |
| D | pm.c | 37 * Restores important CPU context.
65 * ensure that important CPU context is preserved across a CPU power down.
|
| /kernel/linux/linux-5.10/Documentation/process/ |
| D | stable-api-nonsense.rst | 68 isn't that important, but the different data structure padding is
69 very important.
138 important changes that needed to be made, and they were made, with
146 Security issues are also very important for Linux. When a
|
| /kernel/linux/linux-5.10/Documentation/RCU/ |
| D | arrayRCU.rst | 51 Why is it so important that updates be rare when using seqlock?
160 Why is it so important that updates be rare when using seqlock?
162 The reason that it is important that updates be rare when
|
| D | NMI-RCU.rst | 102 Important note: for this to work, the architecture in question must
122 More important, the rcu_dereference_sched() makes it
|
| /kernel/linux/linux-5.10/Documentation/trace/ |
| D | events-kmem.rst | 59 mm_page_alloc_zone_locked event is triggered. This event is important as high
110 successful or not. For some types of hardware, this is important although
113 is important.
|
| /kernel/linux/linux-5.10/Documentation/doc-guide/ |
| D | contributing.rst | 6 Documentation is an important part of any software-development project.
27 important items, but is far from exhaustive; if you see a different way to
49 Another important point is that documentation warnings are often created by
136 times, but it's highly important. If we can actually eliminate warnings
247 Moving documents into the appropriate books is an important task and needs
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smd.txt | 16 are not important.
62 "edge". The names of the devices are not important. The properties of these
|
| /kernel/linux/linux-5.10/kernel/trace/ |
| D | trace_preemptirq.c | 24 * used in the low level entry code where the ordering vs. RCU is important
57 * used in the low level entry code where the ordering vs. RCU is important
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | gl518sm.rst | 29 .. important::
61 zero'; this is important for negative voltage measurements. The VDD input
|
| /kernel/linux/linux-5.10/Documentation/ABI/ |
| D | README | 52 it changes. This is very important for interfaces in
56 important to get feedback for these interfaces to make
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | reporting-bugs.rst | 82 It's REALLY important to report bugs that seem unrelated as separate email
91 The most important information in a bug report is how to reproduce the
108 reports the version of some important subsystems. Run this script with
|
| /kernel/linux/linux-5.10/arch/mips/include/asm/ |
| D | pm.h | 68 /* Save important CPU state for early restoration to global data */
86 /* Restore important CPU state early from global data */
|
| /kernel/linux/linux-5.10/drivers/usb/c67x00/ |
| D | c67x00-hcd.h | 23 * are very important, bandwidth can be sacrificed to guarantee that the
25 * If bulk transfers are important, the MAX_FRAME_BW can be increased,
|
| /kernel/linux/linux-5.10/arch/s390/include/asm/ |
| D | atomic.h | 49 * Order of conditions is important to circumvent gcc 10 bug: in atomic_add()
120 * Order of conditions is important to circumvent gcc 10 bug: in atomic64_add()
|
| /kernel/linux/linux-5.10/arch/parisc/lib/ |
| D | io.c | 163 * IDE driver to read disk sectors. Performance is important, but
235 * SRC. Now works with any alignment in SRC. Performance is important,
333 * driver to write disk sectors. Performance is important, but the
406 * Performance is important, but the interfaces seems to be slow:
|
| /kernel/linux/linux-5.10/Documentation/timers/ |
| D | no_hz.rst | 8 efficiency and reducing OS jitter. Reducing OS jitter is important for
74 scheduling-clock interrupts to idle CPUs, which is critically important
114 and such CPUs are said to be "adaptive-ticks CPUs". This is important
117 duration of a scheduling-clock interrupt. It is also important for
|
| /kernel/linux/linux-5.10/arch/m68k/ |
| D | Makefile | 27 # Enable processor type. Ordering of these is important - we want to
93 # Select the assembler head startup code. Order is important. The default
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | swsusp-dmcrypt.rst | 29 The most important thing is that you set up dm-crypt in such
129 Note that it is important to set the device in /sys/power/resume,
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/nds32/ |
| D | atl2c.txt | 3 The level-2 cache controller plays an important role in reducing memory latency
|
| /kernel/linux/linux-5.10/fs/bfs/ |
| D | Kconfig | 7 allow the bootloader access to the kernel image and other important
|
| /kernel/linux/linux-5.10/arch/nds32/include/asm/ |
| D | stacktrace.h | 16 * IMPORTANT:
|
| /kernel/linux/linux-5.10/net/unix/ |
| D | Kconfig | 18 called unix. Note that several important services won't work
|
| /kernel/linux/linux-5.10/Documentation/core-api/ |
| D | cachetlb.rst | 290 of that page. It is important to flush here to handle
294 The corollary case is just as important, if there are users
320 .. important::
322 It is often important, if you defer the flush,
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/ |
| D | dwc3-cavium.txt | 8 the node is not important. The content of the node is defined in dwc3.txt.
|
12345678910>>...57