| /kernel/linux/linux-5.10/block/partitions/ |
| D | Kconfig | 8 Say Y here if you would like to use hard disks under Linux which
29 Say Y here if you would like to use hard disks under Linux which
42 Say Y here if you would like to use hard disks under Linux which
75 Say Y here if you would like to be able to read the hard disk
87 Say Y here if you would like to use hard disks under Linux which
94 Say Y here if you would like to use hard disks under Linux which
101 Say Y here if you would like to use hard disks under Linux which
108 Say Y here if you would like to be able to read the hard disk
116 Say Y here if you would like to use hard disks under Linux which
180 Say Y here if you would like to use hard disks under Linux which
[all …]
|
| /kernel/linux/linux-6.6/block/partitions/ |
| D | Kconfig | 10 Say Y here if you would like to use hard disks under Linux which
31 Say Y here if you would like to use hard disks under Linux which
44 Say Y here if you would like to use hard disks under Linux which
77 Say Y here if you would like to be able to read the hard disk
89 Say Y here if you would like to use hard disks under Linux which
96 Say Y here if you would like to use hard disks under Linux which
103 Say Y here if you would like to use hard disks under Linux which
110 Say Y here if you would like to be able to read the hard disk
118 Say Y here if you would like to use hard disks under Linux which
182 Say Y here if you would like to use hard disks under Linux which
[all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | directory-locking.rst | 80 the parent of object and it would have to lock the parent).
113 Otherwise the set of contended objects would be infinite - each of them
114 would have a contended child and we had assumed that no object is its
120 would again have an infinite set of contended objects). But that
131 source), such loop would have to contain these objects and the rest of it
132 would have to exist before rename(). I.e. at the moment of loop creation
133 rename() responsible for that would be holding filesystem lock and new parent
134 would have to be equal to or a descendent of source. But that means that
136 we had acquired filesystem lock and rename() would fail with -ELOOP in that
142 also preserved by all operations (cross-directory rename on a tree that would
[all …]
|
| D | ocfs2-online-filecheck.rst | 13 necessary, since turning the filesystem read-only would affect other running
15 Then, a mount option (errors=continue) is introduced, which would return the
34 the offline fsck should/would be recommended.
43 by the inode number which caused the error. This inode number would be the
51 mounted. The file above would accept inode numbers. This could be used to
91 On receiving the inode, the filesystem would read the inode and the
92 file metadata. In case of errors, the filesystem would fix the errors
97 small linked list buffer which would contain the last (N) inodes
|
| /kernel/linux/linux-6.6/Documentation/filesystems/ |
| D | directory-locking.rst | 80 the parent of object and it would have to lock the parent).
113 Otherwise the set of contended objects would be infinite - each of them
114 would have a contended child and we had assumed that no object is its
120 would again have an infinite set of contended objects). But that
131 source), such loop would have to contain these objects and the rest of it
132 would have to exist before rename(). I.e. at the moment of loop creation
133 rename() responsible for that would be holding filesystem lock and new parent
134 would have to be equal to or a descendent of source. But that means that
136 we had acquired filesystem lock and rename() would fail with -ELOOP in that
142 also preserved by all operations (cross-directory rename on a tree that would
[all …]
|
| D | ocfs2-online-filecheck.rst | 13 necessary, since turning the filesystem read-only would affect other running
15 Then, a mount option (errors=continue) is introduced, which would return the
34 the offline fsck should/would be recommended.
43 by the inode number which caused the error. This inode number would be the
51 mounted. The file above would accept inode numbers. This could be used to
91 On receiving the inode, the filesystem would read the inode and the
92 file metadata. In case of errors, the filesystem would fix the errors
97 small linked list buffer which would contain the last (N) inodes
|
| /kernel/linux/linux-5.10/Documentation/w1/masters/ |
| D | ds2490.rst | 32 was added to the API. The name is just a suggestion. It would take
52 clear the entire bulk in buffer. It would be possible to read the
60 with a OHCI controller, ds2490 running in the guest would operate
64 would fail. qemu sets a 50ms timeout and the bulk in would timeout
65 even when the status shows data available. A bulk out write would
66 show a successful completion, but the ds2490 status register would
68 reattaching would clear the problem. usbmon output in the guest and
|
| /kernel/linux/linux-6.6/Documentation/w1/masters/ |
| D | ds2490.rst | 32 was added to the API. The name is just a suggestion. It would take
52 clear the entire bulk in buffer. It would be possible to read the
60 with a OHCI controller, ds2490 running in the guest would operate
64 would fail. qemu sets a 50ms timeout and the bulk in would timeout
65 even when the status shows data available. A bulk out write would
66 show a successful completion, but the ds2490 status register would
68 reattaching would clear the problem. usbmon output in the guest and
|
| /kernel/linux/linux-6.6/drivers/net/wireless/intel/iwlwifi/cfg/ |
| D | 22000.c | 191 * HT size; mac80211 would otherwise pick the HE max (256) by default.
227 * HT size; mac80211 would otherwise pick the HE max (256) by default.
240 * HT size; mac80211 would otherwise pick the HE max (256) by default.
253 * HT size; mac80211 would otherwise pick the HE max (256) by default.
265 * HT size; mac80211 would otherwise pick the HE max (256) by default.
278 * HT size; mac80211 would otherwise pick the HE max (256) by default.
291 * HT size; mac80211 would otherwise pick the HE max (256) by default.
303 * HT size; mac80211 would otherwise pick the HE max (256) by default.
317 * HT size; mac80211 would otherwise pick the HE max (256) by default.
330 * HT size; mac80211 would otherwise pick the HE max (256) by default.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/RCU/ |
| D | UP.rst | 26 from softirq, the list scan would find itself referencing a newly freed
47 its arguments would cause it to fail to make the fundamental guarantee
61 call_rcu() were to directly invoke the callback, the result would
64 In some cases, it would possible to restructure to code so that
69 the same critical section, then the code would need to create
81 or API changes would be required.
127 the process-context critical section. This would result in
141 simply immediately returned, it would prematurely signal the
142 end of the grace period, which would come as a nasty shock to
|
| /kernel/linux/linux-6.6/tools/memory-model/Documentation/ |
| D | README | 8 depending on what you know and what you would like to learn. Please note
14 o You have some background in Linux-kernel concurrency, and would
24 o You are familiar with Linux-kernel concurrency, and would
28 o You would like a detailed understanding of what your compiler can
32 LKMM, and would like a quick reference: cheatsheet.txt
35 of LKMM, and would like to learn about LKMM's requirements,
|
| /kernel/linux/linux-6.6/Documentation/RCU/ |
| D | UP.rst | 26 from softirq, the list scan would find itself referencing a newly freed
47 its arguments would cause it to fail to make the fundamental guarantee
61 call_rcu() were to directly invoke the callback, the result would
65 In some cases, it would possible to restructure to code so that
70 the same critical section, then the code would need to create
82 or API changes would be required.
136 the process-context critical section. This would result in
150 simply immediately returned, it would prematurely signal the
151 end of the grace period, which would come as a nasty shock to
|
| /kernel/linux/linux-5.10/Documentation/bpf/ |
| D | ringbuf.rst | 27 would solve the second problem automatically.
36 One way would be to, similar to ``BPF_MAP_TYPE_PERF_EVENT_ARRAY``, make
38 enforce "same CPU only" rule. This would be more familiar interface compatible
39 with existing perf buffer use in BPF, but would fail if application needed more
42 Additionally, given the performance of BPF ringbuf, many use cases would just
44 approach would be an overkill.
48 with lookup/update/delete operations. This approach would add a lot of extra
50 would also add another concept that BPF developers would have to familiarize
51 themselves with, new syntax in libbpf, etc. But then would really provide no
60 ring buffer for all CPUs, it's as simple and straightforward, as would be with
[all …]
|
| /kernel/linux/linux-6.6/Documentation/bpf/ |
| D | ringbuf.rst | 27 would solve the second problem automatically.
36 One way would be to, similar to ``BPF_MAP_TYPE_PERF_EVENT_ARRAY``, make
38 enforce "same CPU only" rule. This would be more familiar interface compatible
39 with existing perf buffer use in BPF, but would fail if application needed more
42 Additionally, given the performance of BPF ringbuf, many use cases would just
44 approach would be an overkill.
48 with lookup/update/delete operations. This approach would add a lot of extra
50 would also add another concept that BPF developers would have to familiarize
51 themselves with, new syntax in libbpf, etc. But then would really provide no
60 ring buffer for all CPUs, it's as simple and straightforward, as would be with
[all …]
|
| /kernel/linux/linux-6.6/Documentation/networking/ |
| D | snmp_counter.rst | 44 multicast packets, and would always be updated together with
137 would be increased even if the ICMP packet has an invalid type. The
139 IcmpOutMsgs would still be updated if the IP header is constructed by
207 IcmpMsgOutType8 would increase 1. And if kernel gets an ICMP Echo Reply
208 packet, IcmpMsgInType0 would increase 1.
215 IcmpInMsgs would be updated but none of IcmpMsgInType[N] would be updated.
225 counters would be updated. The receiving packet path use IcmpInErrors
227 is increased, IcmpInErrors would always be increased too.
263 packets would be delivered to the TCP layer, but the TCP layer will discard
266 counter would only increase 1.
[all …]
|
| D | x25.rst | 18 implementation of LAPB. Therefore the LAPB modules would be called by
19 unintelligent X.25 card drivers and not by intelligent ones, this would
24 conform with the JNT "Pink Book", this would have a different interface to
25 the Packet Layer but there would be no confusion since the class of device
26 being served by the LLC would be completely separate from LAPB.
|
| /kernel/linux/linux-5.10/Documentation/networking/ |
| D | snmp_counter.rst | 44 multicast packets, and would always be updated together with
137 would be increased even if the ICMP packet has an invalid type. The
139 IcmpOutMsgs would still be updated if the IP header is constructed by
207 IcmpMsgOutType8 would increase 1. And if kernel gets an ICMP Echo Reply
208 packet, IcmpMsgInType0 would increase 1.
215 IcmpInMsgs would be updated but none of IcmpMsgInType[N] would be updated.
225 counters would be updated. The receiving packet path use IcmpInErrors
227 is increased, IcmpInErrors would always be increased too.
263 packets would be delivered to the TCP layer, but the TCP layer will discard
266 counter would only increase 1.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/firmware-guide/acpi/ |
| D | osi.rst | 70 The ACPI BIOS flow would include an evaluation of _OS, and the AML
71 interpreter in the kernel would return to it a string identifying the OS:
83 of every possible version of the OS that would run on it, and needed to know
84 all the quirks of those OS's. Certainly it would make more sense
91 that anybody would install those old operating systems
104 eg. _OSI("3.0 Thermal Model") would return TRUE if the OS knows how
106 An old OS that doesn't know about those extensions would answer FALSE,
121 and its successors. To do otherwise would virtually guarantee breaking
156 which would increment, based on the version of the spec supported.
158 Unfortunately, _REV was also misused. eg. some BIOS would check
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen3/ |
| D | other.json | 22 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
28 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
34 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
40 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
52 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
58 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
64 …Stall. Also counts cycles when the thread is not selected to dispatch but would have been stalled …
|
| /kernel/linux/linux-5.10/Documentation/firmware-guide/acpi/ |
| D | osi.rst | 73 The ACPI BIOS flow would include an evaluation of _OS, and the AML
74 interpreter in the kernel would return to it a string identifying the OS:
86 of every possible version of the OS that would run on it, and needed to know
87 all the quirks of those OS's. Certainly it would make more sense
94 that anybody would install those old operating systems
107 eg. _OSI("3.0 Thermal Model") would return TRUE if the OS knows how
109 An old OS that doesn't know about those extensions would answer FALSE,
124 and its successors. To do otherwise would virtually guarantee breaking
159 which would increment, based on the version of the spec supported.
161 Unfortunately, _REV was also misused. eg. some BIOS would check
|
| /kernel/linux/linux-5.10/drivers/net/wireless/intel/iwlwifi/cfg/ |
| D | 22000.c | 322 * HT size; mac80211 would otherwise pick the HE max (256) by default.
334 * HT size; mac80211 would otherwise pick the HE max (256) by default.
384 * HT size; mac80211 would otherwise pick the HE max (256) by default.
397 * HT size; mac80211 would otherwise pick the HE max (256) by default.
410 * HT size; mac80211 would otherwise pick the HE max (256) by default.
422 * HT size; mac80211 would otherwise pick the HE max (256) by default.
435 * HT size; mac80211 would otherwise pick the HE max (256) by default.
448 * HT size; mac80211 would otherwise pick the HE max (256) by default.
460 * HT size; mac80211 would otherwise pick the HE max (256) by default.
474 * HT size; mac80211 would otherwise pick the HE max (256) by default.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/scsi/ |
| D | lpfc.rst | 36 the LLDD would simply be queued for a short duration, allowing the device
38 to the system. If the driver did not hide these conditions, i/o would be
39 errored by the driver, the mid-layer would exhaust its retries, and the
40 device would be taken offline. Manual intervention would be required to
|
| /kernel/linux/linux-6.6/Documentation/scsi/ |
| D | lpfc.rst | 36 the LLDD would simply be queued for a short duration, allowing the device
38 to the system. If the driver did not hide these conditions, i/o would be
39 errored by the driver, the mid-layer would exhaust its retries, and the
40 device would be taken offline. Manual intervention would be required to
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/device-mapper/ |
| D | log-writes.rst | 31 The log would show the following:
36 cases where a power failure at a particular point in time would create an
42 Any REQ_OP_DISCARD requests are treated like WRITE requests. Otherwise we would
48 If we logged DISCARD when it completed, the replay would look like this:
82 we're fsck'ing something reasonable, you would do something like
89 This would allow you to replay the log up to the mkfs mark and
104 Say you want to test fsync on your file system. You would do something like
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | log-writes.rst | 31 The log would show the following:
36 cases where a power failure at a particular point in time would create an
42 Any REQ_OP_DISCARD requests are treated like WRITE requests. Otherwise we would
48 If we logged DISCARD when it completed, the replay would look like this:
82 we're fsck'ing something reasonable, you would do something like
89 This would allow you to replay the log up to the mkfs mark and
104 Say you want to test fsync on your file system. You would do something like
|