Searched full:course (Results 1 – 25 of 513) sorted by relevance
12345678910>>...21
| /Linux-v6.1/Documentation/filesystems/ext4/ |
| D | allocators.rst | 10 thus speeding up disk IO. On an SSD there of course are no moving parts,
21 unused speculative allocations are of course freed, but if the
55 Of course if all of these mechanisms fail, one can always use e4defrag
|
| D | inlinedata.rst | 12 “system.data” within the inode body (“ibody EA”). This of course
|
| /Linux-v6.1/Documentation/riscv/ |
| D | patch-acceptance.rst | 24 course, maintain their own Linux kernel trees that contain code for
34 (Implementors, may, of course, maintain their own Linux kernel trees
|
| /Linux-v6.1/Documentation/arm/ |
| D | mem_alignment.rst | 13 Of course this is a bad idea to rely on the alignment trap to perform
42 performing the unaligned access. This is of course
|
| /Linux-v6.1/Documentation/driver-api/mtd/ |
| D | nand_ecc.rst | 294 Of course this means some modification as the row parity is byte by
303 Note that of course now the loop is executed only 64 times (256/4).
309 And of course the performance might depend on alignment, but I expect
413 The code (of course) works, and hurray: we are a little bit faster than
422 Of course the same thing holds for rp4/5, rp6/7, rp8/9, rp10/11 and rp12/13.
527 Of course after the loop we need to correct things by adding code like::
606 loop; This eliminates 3 statements per loop. Of course after the loop we
717 factor 18 on my system. Not that bad. Of course on different hardware
720 But of course there is no such thing as a free lunch. The codesize almost
757 programmed in C. Of course it might be possible to squeeze something more
|
| /Linux-v6.1/Documentation/RCU/ |
| D | checklist.rst | 79 from under a lock. Unless, of course, you have arranged some
100 that guard per-element state. Of course, fields that
161 Of course, neither rcu_dereference() nor the "_rcu()"
247 of course a must. One example of non-obvious pairing is
292 RCU grace period. There are of course many other
|
| D | rcubarrier.rst | 27 appropriate lock, of course::
91 There is also an srcu_barrier() function for SRCU, and you of course
197 Of course, if you module uses call_rcu(), you will need to invoke
|
| D | torture.rst | 150 One could of course create a more elaborate script that automatically
203 Of course, each concurrent instance will use memory, which can be
214 This will of course result in the scripting reporting a failure, namely
|
| /Linux-v6.1/Documentation/locking/ |
| D | locktorture.rst | 147 Of course, the same applies for (C), above. A dummy example of this is
163 One could of course create a more elaborate script that automatically
|
| /Linux-v6.1/Documentation/networking/ |
| D | ax25.rst | 16 subscribed to post but of course that means you might miss an answer.
|
| /Linux-v6.1/net/8021q/ |
| D | Kconfig | 12 firewalling, bridging, and of course IP traffic. You will need
|
| /Linux-v6.1/Documentation/doc-guide/ |
| D | contributing.rst | 128 The entire process only took a few minutes. Of course, I then found that
202 The best thing to do, of course, would be to bring the documentation
205 course. Developers are often more than willing to cooperate with people
|
| /Linux-v6.1/include/linux/netfilter_ipv6/ |
| D | ip6_tables.h | 12 * flags are stored in host byte order (of course).
|
| /Linux-v6.1/arch/arc/include/asm/ |
| D | highmem.h | 27 * This should be converted to the asm-generic version, but of course this
|
| /Linux-v6.1/Documentation/powerpc/ |
| D | mpc52xx.rst | 41 - Of course, I inspired myself from the 2.4 port. If you think I forgot to
|
| /Linux-v6.1/drivers/net/can/ctucanfd/ |
| D | Kconfig | 33 The kit description at the Computer Architectures course pages
|
| /Linux-v6.1/Documentation/hwmon/ |
| D | lm95245.rst | 41 channel, but these values are of course linked. Only the local hysteresis
|
| /Linux-v6.1/include/linux/ |
| D | zconf.h | 17 Of course this will generally degrade compression (there's no free lunch).
|
| /Linux-v6.1/drivers/xen/ |
| D | features.c | 25 * mode, of course).
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | sysv-fs.rst | 71 Of course, this affects only the file system, not the data of files on it!
80 Of course, this affects only the file system, not the data of files on it!
|
| /Linux-v6.1/include/linux/netfilter_arp/ |
| D | arp_tables.h | 7 * flags are stored in host byte order (of course).
|
| /Linux-v6.1/samples/bpf/ |
| D | test_probe_write_user_kern.c | 29 * of course, across platforms, and over time, the ABI may change.
|
| /Linux-v6.1/tools/perf/scripts/perl/Perf-Trace-Util/ |
| D | README | 29 generated e.g. blib and shared library, etc, except for of course
|
| /Linux-v6.1/Documentation/driver-api/firmware/ |
| D | firmware-usage-guidelines.rst | 13 then of course these rules will not apply strictly.)
|
| /Linux-v6.1/Documentation/devicetree/bindings/bus/ |
| D | mvebu-mbus.txt | 142 present. Of course, child nodes are needed to probe the devices.
189 possible to choose any address as the base address, provided of course there's
|
12345678910>>...21
