| /kernel/linux/linux-5.10/fs/erofs/ |
| D | xattr.c | 19 static inline void xattr_iter_end(struct xattr_iter *it, bool atomic) in xattr_iter_end() argument
23 kunmap(it->page); in xattr_iter_end()
25 kunmap_atomic(it->kaddr); in xattr_iter_end()
27 unlock_page(it->page); in xattr_iter_end()
28 put_page(it->page); in xattr_iter_end()
31 static inline void xattr_iter_end_final(struct xattr_iter *it) in xattr_iter_end_final() argument
33 if (!it->page) in xattr_iter_end_final()
36 xattr_iter_end(it, true); in xattr_iter_end_final()
42 struct xattr_iter it; in init_inode_xattrs() local
70 * 1) it is not enough to contain erofs_xattr_ibody_header then in init_inode_xattrs()
[all …]
|
| /kernel/linux/linux-6.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 …]
|
| /kernel/linux/linux-6.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 …]
|
| /kernel/linux/linux-5.10/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
54 synthesizer. You can say y to build it into the kernel,
55 or m to build it as a module. See the configuration
63 synthesizer. You can say y to build it into the kernel,
64 or m to build it as a module. See the configuration
71 synthesizer. You can say y to build it into the kernel,
72 or m to build it as a module. See the configuration
79 You can say y to build it into the kernel, or m to
80 build it as a module. See the configuration help on the
[all …]
|
| /kernel/linux/linux-6.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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.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 …]
|
| /kernel/linux/linux-5.10/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 identity string of
20 It is a read/write file. While reading, it gives '1'
22 it gives '0'. Writing a '1' to the file enables the
32 It is a read only file. It gives active/inactive status of
39 It is a read only file. It contains watchdog device's
40 internal status bits. It is equivalent to WDIOC_GETSTATUS
47 It is a read only file. It contains value of time left for
48 reset generation. It is equivalent to WDIOC_GETTIMELEFT of
[all …]
|
| /kernel/linux/linux-6.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 …]
|
| /kernel/linux/linux-5.10/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 | 58 informative error value to report). Call it foo_fill_super(). Now declare::
89 it by internal locking (most of filesystems couldn't care less) - you
98 and ->readdir() are called without BKL now. Grab it on entry, drop upon return
109 individual fs sb_op functions. If you don't need it, remove it.
116 free to drop it...
130 an existing filesystem, set it according to ->fs_flags::
136 FS_LITTER is gone - just remove it from fs_flags.
143 went in - and hadn't been documented ;-/). Just remove it from fs_flags
163 Briefly it allows for the definition of decode_fh and encode_fh operations
168 It is planned that this will be required for exporting once the code
[all …]
|
| /kernel/linux/linux-6.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 …]
|
| /kernel/linux/linux-6.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 …]
|
| /kernel/linux/linux-5.10/net/netfilter/ipvs/ |
| D | Kconfig | 24 If you want to compile it in kernel, say Y. To compile it as a
59 performance on it. You can adapt the table size yourself, according
60 to your virtual server application. It is good to set the table size
65 should be not far less than 200x200, it is good to set the table
120 If you want to compile it in kernel, say Y. To compile it as a
133 If you want to compile it in kernel, say Y. To compile it as a
143 If you want to compile it in kernel, say Y. To compile it as a
153 If you want to compile it in kernel, say Y. To compile it as a
163 If you want to compile it in kernel, say Y. To compile it as a
174 If you want to compile it in kernel, say Y. To compile it as a
[all …]
|
| /kernel/linux/linux-6.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 …]
|
| /kernel/linux/linux-6.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 …]
|
| /kernel/linux/linux-6.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
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.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 …]
|
| /kernel/linux/linux-5.10/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 …]
|