| /Linux-v6.6/fs/erofs/ |
| D | xattr.c | 31 struct erofs_xattr_iter it; in erofs_init_inode_xattrs() local
57 * 1) it is not enough to contain erofs_xattr_ibody_header then in erofs_init_inode_xattrs()
58 * ->xattr_isize should be 0 (it means no xattr); in erofs_init_inode_xattrs()
59 * 2) it is just to contain erofs_xattr_ibody_header, which is on-disk in erofs_init_inode_xattrs()
79 it.buf = __EROFS_BUF_INITIALIZER; in erofs_init_inode_xattrs()
80 erofs_init_metabuf(&it.buf, sb); in erofs_init_inode_xattrs()
81 it.pos = erofs_iloc(inode) + vi->inode_isize; in erofs_init_inode_xattrs()
84 it.kaddr = erofs_bread(&it.buf, erofs_blknr(sb, it.pos), EROFS_KMAP); in erofs_init_inode_xattrs()
85 if (IS_ERR(it.kaddr)) { in erofs_init_inode_xattrs()
86 ret = PTR_ERR(it.kaddr); in erofs_init_inode_xattrs()
[all …]
|
| /Linux-v6.6/tools/testing/selftests/bpf/progs/ |
| D | iters.c | 27 struct bpf_iter_num it; in iter_err_unsafe_c_loop() local
32 bpf_iter_num_new(&it, 0, 1000); in iter_err_unsafe_c_loop()
33 while ((v = bpf_iter_num_next(&it))) { in iter_err_unsafe_c_loop()
36 bpf_iter_num_destroy(&it); in iter_err_unsafe_c_loop()
47 struct bpf_iter_num it; in iter_err_unsafe_asm_loop() local
53 "r1 = %[it];" /* iterator state */ in iter_err_unsafe_asm_loop()
59 "r1 = %[it];" in iter_err_unsafe_asm_loop()
65 "r1 = %[it];" in iter_err_unsafe_asm_loop()
73 : [it]"r"(&it), in iter_err_unsafe_asm_loop()
89 struct bpf_iter_num it; in iter_while_loop() local
[all …]
|
| D | iters_num.c | 142 struct bpf_iter_num it; in num_invalid_range() local
144 res_invalid_range = bpf_iter_num_new(&it, 1, 0); in num_invalid_range()
145 bpf_iter_num_destroy(&it); in num_invalid_range()
156 struct bpf_iter_num it; in num_max_range() local
158 res_max_range = 10 + bpf_iter_num_new(&it, 0, BPF_MAX_LOOPS); in num_max_range()
159 bpf_iter_num_destroy(&it); in num_max_range()
170 struct bpf_iter_num it; in num_e2big_range() local
172 res_e2big_range = bpf_iter_num_new(&it, -1, BPF_MAX_LOOPS); in num_e2big_range()
173 bpf_iter_num_destroy(&it); in num_e2big_range()
184 struct bpf_iter_num it; in num_succ_elem_cnt() local
[all …]
|
| /Linux-v6.6/Documentation/ABI/testing/ |
| D | sysfs-class-watchdog | 5 It is a read only file. It contains status of the watchdog
6 device at boot. It is equivalent to WDIOC_GETBOOTSTATUS of
13 It is a read only file. It contains options of watchdog device.
19 It is a read only file. It contains firmware version of
26 It is a read only file. It contains identity string of
33 It is a read/write file. While reading, it gives '1'
35 it gives '0'. Writing a '1' to the file enables the
45 It is a read only file. It gives active/inactive status of
52 It is a read only file. It contains watchdog device's
53 internal status bits. It is equivalent to WDIOC_GETSTATUS
[all …]
|
| /Linux-v6.6/Documentation/process/ |
| D | management-style.rst | 7 on who you ask) management style for the linux kernel. It's meant to
14 to do with reality. It started as a lark, but that doesn't mean that it
17 Btw, when talking about "kernel manager", it's all about the technical
24 People", and NOT read it. Burn it, it's a great symbolic gesture.
27 making it painfully obvious to the questioner that we don't have a clue
39 manager must be to make it. That's very deep and obvious, but it's not
60 It helps to realize that the key difference between a big decision and a
75 It turns out that since nobody would be stupid enough to ever really let
76 a kernel manager have huge fiscal responsibility **anyway**, it's usually
83 you made a year ago wasn't a big decision after all, since it could be
[all …]
|
| /Linux-v6.6/drivers/accessibility/speakup/ |
| D | Kconfig | 8 This is the Speakup screen reader. Think of it as a
10 kernel, it can speak everything on the text console from
55 synthesizer. You can say y to build it into the kernel,
56 or m to build it as a module. See the configuration
64 synthesizer. You can say y to build it into the kernel,
65 or m to build it as a module. See the configuration
72 synthesizer. You can say y to build it into the kernel,
73 or m to build it as a module. See the configuration
80 You can say y to build it into the kernel, or m to
81 build it as a module. See the configuration help on the
[all …]
|
| /Linux-v6.6/Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 20 a program is suspended and instructions belonging to it are not fetched from
25 it is an opportunity to save energy.
39 (program) from memory and executing them, but it need not work this way
43 program) at a time, it is a CPU. In that case, if the hardware is asked to
46 Second, if the processor is multi-core, each core in it is able to follow at
52 enter an idle state, that applies to the core that asked for it in the first
53 place, but it also may apply to a larger unit (say a "package" or a "cluster")
54 that the core belongs to (in fact, it may apply to an entire hierarchy of larger
57 remaining core asks the processor to enter an idle state, that may trigger it
70 by one of them, the hardware thread (or CPU) that asked for it is stopped, but
[all …]
|
| D | cpufreq.rst | 28 In some situations it is desirable or even necessary to run the program as fast
31 available). In some other cases, however, it may not be necessary to execute
33 relatively long time without utilizing it entirely may be regarded as wasteful.
34 It also may not be physically possible to maintain maximum CPU capacity for too
44 to as CPU performance scaling or CPU frequency scaling (because it involves
56 interfaces for all platforms that support CPU performance scaling. It defines
71 platform-independent form in the majority of cases, so it should be possible
79 interface it comes from and may not be easily represented in an abstract,
90 control the P-state of multiple CPUs at the same time and writing to it affects
111 It is only possible to register one scaling driver at a time, so the scaling
[all …]
|
| D | sleep-states.rst | 21 Depending on its configuration and the capabilities of the platform it runs on,
32 referred to as S2I or S2Idle). It allows more energy to be saved relative to
43 or :ref:`suspend-to-RAM <s2ram>`, or it can be used in addition to any of the
44 deeper system suspend variants to provide reduced resume latency. It is always
55 go back to where it left off easily enough.
60 are suspended during transitions into this state. For this reason, it should
65 reduced relative to :ref:`suspend-to-idle <s2idle>` and it may be necessary to
69 option is set and the support for it is registered by the platform with the
94 platform firmware to resume the system from it. This may be the case on other
98 relative to :ref:`suspend-to-idle <s2idle>` and :ref:`standby <standby>` and it
[all …]
|
| /Linux-v6.6/Documentation/filesystems/ |
| D | hpfs.rst | 15 is taken from it
24 Set owner/group/mode for files that do not have it specified in extended
33 - there is a list of text extensions (I thing it's better to not convert
35 change it in the source. Original readonly HPFS contained some strange
36 heuristic algorithm that I removed. I thing it's danger to let the
42 danger. I tried to write it so that it won't crash if check=normal on
44 used for debugging (for example it checks if file is allocated in
45 bitmaps when accessing it).
49 When to mark filesystem dirty so that OS/2 checks it.
72 access it under names 'a.', 'a..', 'a . . . ' etc.
[all …]
|
| D | path-lookup.rst | 12 It has subsequently been updated to reflect changes in the kernel
22 exploration is needed to discover, is that it is complex. There are
25 acquainted with such complexity and has tools to help manage it. One
51 It is tempting to describe the second kind as starting with a
53 slashes and components, it can be empty, in other words. This is
55 in Linux permit it when the ``AT_EMPTY_PATH`` flag is given. For
57 can execute it by calling `execveat() <execveat_>`_ passing
62 it must identify a directory that already exists, otherwise an error
66 calls interpret it quite differently (e.g. some create it, some do
67 not), but it might not even exist: neither the empty pathname nor the
[all …]
|
| D | porting.rst | 64 informative error value to report). Call it foo_fill_super(). Now declare::
95 it by internal locking (most of filesystems couldn't care less) - you
104 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
115 individual fs sb_op functions. If you don't need it, remove it.
122 free to drop it...
136 an existing filesystem, set it according to ->fs_flags::
142 FS_LITTER is gone - just remove it from fs_flags.
149 went in - and hadn't been documented ;-/). Just remove it from fs_flags
169 Briefly it allows for the definition of decode_fh and encode_fh operations
174 It is planned that this will be required for exporting once the code
[all …]
|
| D | xfs-self-describing-metadata.rst | 14 adequate for supporting PB scale filesystems with billions of inodes, however it
24 For example, it is entirely possible to manually use xfs_db and a bit of
26 determine the root cause of a corruption problem, but it is still mainly a
28 weren't the ultimate cause of a corruption event. It may take a few hours to a
44 magic number in the metadata block, we have no other way of identifying what it
45 is supposed to be. We can't even identify if it is the right place. Put simply,
46 you can't look at a single metadata block in isolation and say "yes, it is
54 went wrong, but it is impossible to tell what order the blocks were linked into
74 numbers in the metadata objects. That is, if it has the current magic number,
75 the metadata isn't self identifying. If it contains a new magic number, it is
[all …]
|
| D | autofs.rst | 2 autofs - how it works
59 always a regular directory, otherwise it is a mount trap when it is
69 option and particularly whether it is less than five or not.
91 the inode has S_AUTOMOUNT set, or can be set directly) then it is
95 should be mounted on the directory and to return it. The VFS is
100 automount daemon asking it to find and mount the filesystem. The
102 everything is ready. It will then return "`NULL`" indicating that the
108 reflected on the client. However it is not sufficient for autofs. As
122 to `false`. It may return one of three things:
137 autofs returns this if it detects that the process performing the
[all …]
|
| /Linux-v6.6/Documentation/filesystems/caching/ |
| D | netfs-api.rst | 63 blob into something it can use and may employ hash tables, trees or whatever to
67 A filesystem would typically have a cookie for each inode, and would acquire it
68 in iget and relinquish it when evicting the cookie.
70 Once it has a cookie, the filesystem needs to mark the cookie as being in use.
76 unuse it in file release and it needs to use the cookie around calls to
77 truncate the cookie locally. It *also* needs to use the cookie when the
78 pagecache becomes dirty and unuse it when writeback is complete. This is
79 slightly tricky, and provision is made for it.
88 actually required and it can use the fscache I/O API directly.
95 volume it wants to access::
[all …]
|
| /Linux-v6.6/Documentation/translations/it_IT/process/ |
| D | programming-language.rst | 4 :Translator: Federico Vaga <federico.vaga@vaga.pv.it>
11 Il kernel è scritto nel linguaggio di programmazione C [it-c-language]_.
12 Più precisamente, il kernel viene compilato con ``gcc`` [it-gcc]_ usando
13 l'opzione ``-std=gnu11`` [it-gcc-c-dialect-options]_: il dialetto GNU
15 Linux supporta anche ``clang`` [it-clang]_, leggete la documentazione
18 Questo dialetto contiene diverse estensioni al linguaggio [it-gnu-extensions]_,
25 [it-gcc-attribute-syntax]_. Gli attributi permettono di aggiungere una semantica,
28 linguaggio stesso (come l'aggiunta di nuove parole chiave) [it-n2049]_.
46 [it-rust-language]_ abilitando l'opzione di configurazione ``CONFIG_RUST``. Il
47 codice verrà compilato usando ``rustc`` [it-rustc]_ con l'opzione
[all …]
|
| /Linux-v6.6/net/netfilter/ipvs/ |
| D | Kconfig | 24 If you want to compile it in kernel, say Y. To compile it as a
60 small, otherwise you will lose performance on it. You can adapt the
62 It is good to set the table size not far less than the number of
67 less than 200x200, it is good to set the table size 32768 (2**15).
121 If you want to compile it in kernel, say Y. To compile it as a
134 If you want to compile it in kernel, say Y. To compile it as a
144 If you want to compile it in kernel, say Y. To compile it as a
154 If you want to compile it in kernel, say Y. To compile it as a
164 If you want to compile it in kernel, say Y. To compile it as a
175 If you want to compile it in kernel, say Y. To compile it as a
[all …]
|
| /Linux-v6.6/drivers/misc/vmw_vmci/ |
| D | vmci_route.c | 18 * devices. Will set the source context if it is invalid.
33 * which comes from the VMX, so we know it is coming from a in vmci_route()
50 * cannot send it to the hypervisor. It must come in vmci_route()
69 * respect it (both context and resource are invalid). in vmci_route()
72 * should set the real context here before passing it in vmci_route()
87 * If it is not from a guest but we are acting as a in vmci_route()
88 * guest, then we need to send it down to the host. in vmci_route()
99 * itself, but it will never send datagrams to in vmci_route()
116 /* Send it from local client down to the host. */ in vmci_route()
122 * Otherwise we already received it from a guest and in vmci_route()
[all …]
|
| /Linux-v6.6/drivers/net/wireless/realtek/rtlwifi/ |
| D | Kconfig | 24 If you choose to build it as a module, it will be called rtl8192ce
35 If you choose to build it as a module, it will be called rtl8192se
46 If you choose to build it as a module, it will be called rtl8192de
59 If you choose to build it as a module, it will be called rtl8723ae
72 If you choose to build it as a module, it will be called rtl8723be
83 If you choose to build it as a module, it will be called rtl8188ee
95 If you choose to build it as a module, it will be called rtl8192ee
107 If you choose to build it as a module, it will be called rtl8821ae
119 If you choose to build it as a module, it will be called rtl8192cu
|
| /Linux-v6.6/Documentation/userspace-api/media/dvb/ |
| D | frontend-stat-properties.rst | 16 It should be noted, however, that new OFDM delivery systems like ISDB
36 - ``scale`` - Scale for the value. It can be:
39 frontend, but it was not possible to collect it (could be a
63 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the
82 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the
103 In order to get the BER (Bit Error Rate) measurement, it should be
108 bit count measurements. The frontend may reset it when a
113 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the
130 It should be noted that this measurement can be smaller than the total
136 bit count measurements. The frontend may reset it when a
[all …]
|
| /Linux-v6.6/Documentation/power/ |
| D | pci.rst | 34 Usually, a device is put into a low-power state when it is underutilized or
35 completely inactive. However, when it is necessary to use the device once
36 again, it has to be put back into the "fully functional" state (full-power
53 to put the device that sent it into the full-power state. However, the PCI Bus
56 It is assumed that the platform firmware will perform this task and therefore,
57 even though a PCI device is set up to generate PMEs, it also may be necessary to
63 preparing the device to generate wakeup signals. In that case, however, it
75 introduced between the PCI 2.1 and PCI 2.2 Specifications. It defined a
80 but it is mandatory for PCI Express devices. If a device supports the PCI PM
81 Spec, it has an 8 byte power management capability field in its PCI
[all …]
|
| /Linux-v6.6/Documentation/fb/ |
| D | matroxfb.rst | 13 * It provides a nice large console (128 cols + 48 lines with 1024x768)
24 How to use it?
93 XF{68,86}_FBDev should work just fine, but it is non-accelerated. On non-intel
108 Driver contains SVGALib compatibility code. It is turned on by choosing textual
109 mode for console. You can do it at boot time by using videomode
112 Switching to another console and back fixes it. I hope that it is SVGALib's
127 it always probe for memory. Default is to use whole detected
132 configuration, you can override it by this (you cannot override
133 `off`). It is default.
134 noaccel do not use acceleration engine. It does not work on Alphas.
[all …]
|
| /Linux-v6.6/Documentation/security/keys/ |
| D | request-key.rst | 46 does not need to link the key to a keyring to prevent it from being immediately
48 it's up to the caller to destroy the key.
50 The request_key_tag() call is like the in-kernel request_key(), except that it
59 The request_key_rcu() call is like the request_key_tag() call, except that it
82 a suitable key there. If there is, it returns the key. If there isn't,
86 3) request_key() sees that A doesn't have the desired key yet, so it creates
104 Kerberos TGT key). It just requests the appropriate key, and the keyring
107 This will permit it to then search the keyrings of process A with the
108 UID, GID, groups and security info of process A as if it was process A,
111 8) The program then does what it must to get the data with which to
[all …]
|
| /Linux-v6.6/Documentation/driver-api/usb/ |
| D | persist.rst | 20 required to behave as though the device has been unplugged. It's a
23 device is still attached or perhaps it was removed and a different
29 though they had disconnected. This is always safe and it is the
35 system woke up, who cares? It'll still work the same when you type on
36 it.
52 it's as though you had unplugged all the USB devices. Yes, it's
64 the system can't be suspended at all. (All right, it _can_ be
65 suspended -- but it will crash as soon as it wakes up, which isn't
72 The kernel includes a feature called USB-persist. It tries to work
76 It works like this. If the kernel sees that a USB host controller is
[all …]
|
| /Linux-v6.6/Documentation/admin-guide/ |
| D | reporting-issues.rst | 16 <https://kernel.org/>`_. If it still shows the issue, report it to the stable
29 The issue was fixed there, but you would like to see it resolved in a still
31 If it shows the problem, search for the change that fixed it in mainline and
32 check if backporting is in the works or was discarded; if it's neither, ask
33 those who handled the change for it.
36 ensure it's vanilla (IOW: not patched and not using add-on modules). Also make
37 sure it's built and running in a healthy environment and not already tainted
55 developers. It might be all that's needed for people already familiar with
57 everyone else there is this section. It is more detailed and uses a
58 step-by-step approach. It still tries to be brief for readability and leaves
[all …]
|
