| /Linux-v5.4/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
64 * 1) it is not enough to contain erofs_xattr_ibody_header then in init_inode_xattrs()
[all …]
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | hpfs.txt | 9 is taken from it
16 Set owner/group/mode for files that do not have it specified in extended
25 - there is a list of text extensions (I thing it's better to not convert
27 change it in the source. Original readonly HPFS contained some strange
28 heuristic algorithm that I removed. I thing it's danger to let the
34 danger. I tried to write it so that it won't crash if check=normal on
36 used for debugging (for example it checks if file is allocated in
37 bitmaps when accessing it).
41 When to mark filesystem dirty so that OS/2 checks it.
63 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
21 exploration is needed to discover, is that it is complex. There are
24 acquainted with such complexity and has tools to help manage it. One
50 It is tempting to describe the second kind as starting with a
52 slashes and components, it can be empty, in other words. This is
54 in Linux permit it when the ``AT_EMPTY_PATH`` flag is given. For
56 can execute it by calling `execveat() <execveat_>`_ passing
61 it must identify a directory that already exists, otherwise an error
65 calls interpret it quite differently (e.g. some create it, some do
66 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 …]
|
| D | xfs-self-describing-metadata.txt | 10 adequate for supporting PB scale filesystems with billions of inodes, however it
20 For example, it is entirely possible to manually use xfs_db and a bit of
22 determine the root cause of a corruption problem, but it is still mainly a
24 weren't the ultimate cause of a corruption event. It may take a few hours to a
40 magic number in the metadata block, we have no other way of identifying what it
41 is supposed to be. We can't even identify if it is the right place. Put simply,
42 you can't look at a single metadata block in isolation and say "yes, it is
50 went wrong, but it is impossible to tell what order the blocks were linked into
70 numbers in the metadata objects. That is, if it has the current magic number,
71 the metadata isn't self identifying. If it contains a new magic number, it is
[all …]
|
| D | autofs.txt | 5 autofs - how it works
61 always a regular directory, otherwise it is a mount trap when it is
71 option and particularly whether it is less than five or not.
93 the inode has S_AUTOMOUNT set, or can be set directly) then it is
97 should be mounted on the directory and to return it. The VFS is
102 automount daemon asking it to find and mount the filesystem. The
104 everything is ready. It will then return "`NULL`" indicating that the
110 reflected on the client. However it is not sufficient for autofs. As
124 to `false`. It may return one of three things:
139 autofs returns this if it detects that the process performing the
[all …]
|
| /Linux-v5.4/drivers/staging/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
49 synthesizer. You can say y to build it into the kernel,
50 or m to build it as a module. See the configuration
58 synthesizer. You can say y to build it into the kernel,
59 or m to build it as a module. See the configuration
66 synthesizer. You can say y to build it into the kernel,
67 or m to build it as a module. See the configuration
74 You can say y to build it into the kernel, or m to
75 build it as a module. See the configuration help on the
[all …]
|
| /Linux-v5.4/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 | 29 In some situations it is desirable or even necessary to run the program as fast
32 available). In some other cases, however, it may not be necessary to execute
34 relatively long time without utilizing it entirely may be regarded as wasteful.
35 It also may not be physically possible to maintain maximum CPU capacity for too
45 to as CPU performance scaling or CPU frequency scaling (because it involves
57 interfaces for all platforms that support CPU performance scaling. It defines
72 platform-independent form in the majority of cases, so it should be possible
80 interface it comes from and may not be easily represented in an abstract,
91 control the P-state of multiple CPUs at the same time and writing to it affects
112 It is only possible to register one scaling driver at a time, so the scaling
[all …]
|
| /Linux-v5.4/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-v5.4/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 only file. While reading, it gives '1' if that
21 device supports nowayout feature else, it gives '0'.
27 It is a read only file. It gives active/inactive status of
34 It is a read only file. It contains watchdog device's
35 internal status bits. It is equivalent to WDIOC_GETSTATUS
42 It is a read only file. It contains value of time left for
43 reset generation. It is equivalent to WDIOC_GETTIMELEFT of
[all …]
|
| /Linux-v5.4/net/netfilter/ipvs/ |
| D | Kconfig | 24 If you want to compile it in kernel, say Y. To compile it as a
60 performance on it. You can adapt the table size yourself, according
61 to your virtual server application. It is good to set the table size
66 should be not far less than 200x200, it is good to set the table
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-v5.4/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-v5.4/Documentation/media/uapi/dvb/ |
| D | frontend-stat-properties.rst | 8 .. TODO: replace it to GFDL-1.1-or-later WITH no-invariant-sections
23 It should be noted, however, that new OFDM delivery systems like ISDB
43 - ``scale`` - Scale for the value. It can be:
46 frontend, but it was not possible to collect it (could be a
70 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the
89 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the
110 In order to get the BER (Bit Error Rate) measurement, it should be
115 bit count measurements. The frontend may reset it when a
120 - ``FE_SCALE_NOT_AVAILABLE`` - it failed to measure it, or the
137 It should be noted that this measurement can be smaller than the total
[all …]
|
| /Linux-v5.4/Documentation/filesystems/configfs/ |
| D | configfs.txt | 20 is discovered) and it is registered with sysfs. Its attributes then
22 readdir(3)/read(2). It may allow some attributes to be modified via
28 mkdir(2). It is destroyed via rmdir(2). The attributes appear at
41 it by doing
47 subsystems. Once a client subsystem is loaded, it will appear as a
70 write_bin_attribute method will be invoked on the final close, therefore it is
76 When an item needs to be destroyed, remove it with rmdir(2). An
77 item cannot be destroyed if any other item has a link to it (via
83 access remote block devices. Call it FakeNBD. FakeNBD uses configfs
86 the driver about it. Here's where configfs comes in.
[all …]
|
| /Linux-v5.4/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-v5.4/include/drm/ |
| D | drm_bridge.h | 11 * about the suitability of this software for any purpose. It is provided "as
68 * restriction in the modes it can display. For example, a given bridge
75 * drm_helper_probe_single_connector_modes(), and it is used by the
84 * commit, and the mode validation in the probe paths it is not allowed
85 * to look at anything else but the passed-in mode, and validate it
104 * requires. It can be modified by this callback and does not need to
138 * This callback should disable the bridge. It is called right before
140 * preceding element is a bridge this means it's called before that
142 * it's called right before the &drm_encoder_helper_funcs.disable,
147 * signals) feeding it is still running when this callback is called.
[all …]
|
| /Linux-v5.4/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-v5.4/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-v5.4/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-v5.4/drivers/gpu/drm/nouveau/nvkm/subdev/mmu/ |
| D | vmm.c | 98 nvkm_vmm_trace(struct nvkm_vmm_iter *it, char *buf) in nvkm_vmm_trace() argument
101 for (lvl = it->max; lvl >= 0; lvl--) { in nvkm_vmm_trace()
102 if (lvl >= it->lvl) in nvkm_vmm_trace()
103 buf += sprintf(buf, "%05x:", it->pte[lvl]); in nvkm_vmm_trace()
120 nvkm_vmm_flush_mark(struct nvkm_vmm_iter *it) in nvkm_vmm_flush_mark() argument
122 it->flush = min(it->flush, it->max - it->lvl); in nvkm_vmm_flush_mark()
126 nvkm_vmm_flush(struct nvkm_vmm_iter *it) in nvkm_vmm_flush() argument
128 if (it->flush != NVKM_VMM_LEVELS_MAX) { in nvkm_vmm_flush()
129 if (it->vmm->func->flush) { in nvkm_vmm_flush()
130 TRA(it, "flush: %d", it->flush); in nvkm_vmm_flush()
[all …]
|
| /Linux-v5.4/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 …]
|
| D | swsusp.rst | 21 it may cause some problems, too. If you change kernel command line
22 between suspend and resume, it may do something wrong. If you change
23 your hardware while system is suspended... well, it was not good idea;
24 but it will probably only crash.
26 ( ) suspend/resume support is needed to make it safe.
36 line or specify it using /sys/power/resume.
40 resume_offset=<number> on the kernel command line or specify it
52 to RAM (provided your platform supports it), you can try::
66 before suspend (it is limited to around 2/5 of available RAM by default).
69 if found, it then checks the contents for the hibernation image signature.
[all …]
|
| /Linux-v5.4/tools/testing/selftests/bpf/verifier/ |
| D | var_off.c | 6 /* Make it small and 4-byte aligned */
8 /* add it to skb. We now have either &skb->len or
12 /* dereference it */
27 /* Make it small and 4-byte aligned */
30 /* add it to fp. We now have either fp-4 or fp-8, but
34 /* dereference it */
61 /* Dereference it indirectly. */
77 /* Make it small and 4-byte aligned */
80 /* add it to fp. We now have either fp-4 or fp-8, but
84 /* dereference it indirectly */
[all …]
|
| /Linux-v5.4/include/linux/ |
| D | iversion.h | 13 * metadata since it was last queried.
15 * Observers see the i_version as a 64-bit number that never decreases. If it
16 * remains the same since it was last checked, then nothing has changed in the
17 * inode. If it's different then something has changed. Observers cannot infer
27 * the VFS will not touch it on writes, and the filesystem can use it how it
32 * It may be impractical for filesystems to keep i_version updates atomic with
35 * them. Also, i_version updates should never be delayed longer than it takes
39 * track when the value has been queried. If it has not been queried since it
44 * fashion, we might as well increment it as well.
47 * increase over time if the file has changed. It's recommended to use
[all …]
|
