| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 6 Some regulator directories will contain a field called
32 Some regulator directories will contain a field called
96 Some regulator directories will contain a field called
111 Some regulator directories will contain a field called
126 Some regulator directories will contain a field called
151 Some regulator directories will contain a field called
166 Some regulator directories will contain a field called
181 Some regulator directories will contain a field called
196 Some regulator directories will contain a field called
234 Some regulator directories will contain a field called
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 6 Some regulator directories will contain a field called
32 Some regulator directories will contain a field called
96 Some regulator directories will contain a field called
111 Some regulator directories will contain a field called
126 Some regulator directories will contain a field called
151 Some regulator directories will contain a field called
166 Some regulator directories will contain a field called
181 Some regulator directories will contain a field called
196 Some regulator directories will contain a field called
234 Some regulator directories will contain a field called
[all …]
|
| /kernel/linux/linux-4.19/Documentation/filesystems/ |
| D | overlayfs.txt | 23 While directories will report an st_dev from the overlay-filesystem,
56 'lower' filesystem is either hidden or, in the case of directories,
74 Directories
77 Overlaying mainly involves directories. If a given name appears in both
82 Where both upper and lower objects are directories, a merged directory
85 At mount time, the two directories given as mount options "lowerdir" and
97 actual lookups find directories, both are stored and a merged
101 Only the lists of names from directories are merged. Other content
105 whiteouts and opaque directories
111 directories (non-directories are always opaque).
[all …]
|
| D | squashfs.txt | 6 directories. Inodes in the system are very small and all blocks are packed to
28 Max directories: unlimited unlimited
44 Squashfs compresses data, inodes and directories. In addition, inode and
109 Metadata (inodes and directories) are compressed in 8Kbyte blocks. Each
126 regular files and directories, and extended types where extra
129 3.3 Directories
132 Like inodes, directories are packed into compressed metadata blocks, stored
133 in a directory table. Directories are accessed using the start address of
137 Directories are organised in a slightly complex way, and are not simply
141 Directories are therefore organised in a two level list, a directory
[all …]
|
| D | autofs.txt | 48 An autofs filesystem can contain 3 sorts of objects: directories,
49 symbolic links and mount traps. Mount traps are directories with
53 created with a regular `symlink` system call, while directories and
67 Directories created in the root directory are mount traps only if the
70 Directories further down the tree depend on the *maxproto* mount
72 When *maxproto* is five, no directories further down the
73 tree are ever mount traps, they are always regular directories. When
74 the *maxproto* is four (or three), these directories are mount traps
77 So: non-empty (i.e. non-leaf) directories are never mount traps. Empty
78 directories are sometimes mount traps, and sometimes not depending on
[all …]
|
| D | omfs.txt | 8 block sizes from 2k to 8k, with hash-based directories. This
36 dmask=xxx - set umask to xxx for directories
63 Files and directories are both represented by omfs_inode:
78 Directories in OMFS are implemented as a large hash table. Filenames are
|
| D | fscrypt.rst | 9 transparent encryption of files and directories.
46 userspace provides the key, all regular files, directories, and
173 length. Truncation is the norm for directories and symlinks, since
293 files, directories (recursively), and symlinks created in the
301 regular files and directories, including nonempty directories.
421 With the encryption key, encrypted regular files, directories, and
475 files, directories, and symlinks even before their encryption key has
480 - Directories may be listed, in which case the filenames will be
492 with unlink() as usual, and empty directories may be deleted with
497 in encrypted form, similar to filenames in directories. Hence, they
[all …]
|
| D | ceph.txt | 19 * Recursive accounting (nested files, directories, bytes)
41 directories, allowing entire directories of dentries and inodes to be
43 extremely large directories can be fragmented and managed by
58 Ceph also provides some recursive accounting on directories for nested
|
| D | hpfs.txt | 154 You encounter this problem only if you have many directories so that
158 You can't delete open directories.
160 You can't rename over directories (what is it good for?).
170 (lost files, unbalanced directories). (I guess all filesystem may do it).
183 probably because of directories created with old version of this driver.
191 When you have two (or more) lost directories pointing each to other, chkdsk
248 Directories have no longer archive attribute set (some programs don't like
255 error sometimes when opening directories in PMSHELL)
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | autofs.rst | 45 An autofs filesystem can contain 3 sorts of objects: directories,
46 symbolic links and mount traps. Mount traps are directories with
50 created with a regular `symlink` system call, while directories and
53 map is consulted by autofs to determine which directories are mount
65 Directories created in the root directory are mount traps only if the
68 Directories further down the tree depend on the *maxproto* mount
70 When *maxproto* is five, no directories further down the
71 tree are ever mount traps, they are always regular directories. When
72 the *maxproto* is four (or three), these directories are mount traps
75 So: non-empty (i.e. non-leaf) directories are never mount traps. Empty
[all …]
|
| D | overlayfs.rst | 25 While directories will report an st_dev from the overlay-filesystem,
91 'lower' filesystem is either hidden or, in the case of directories,
109 Directories chapter
112 Overlaying mainly involves directories. If a given name appears in both
117 Where both upper and lower objects are directories, a merged directory
120 At mount time, the two directories given as mount options "lowerdir" and
132 actual lookups find directories, both are stored and a merged
136 Only the lists of names from directories are merged. Other content
140 whiteouts and opaque directories
146 directories (non-directories are always opaque).
[all …]
|
| D | squashfs.rst | 10 directories. Inodes in the system are very small and all blocks are packed to
33 Max directories unlimited unlimited
50 Squashfs compresses data, inodes and directories. In addition, inode and
115 Metadata (inodes and directories) are compressed in 8Kbyte blocks. Each
132 regular files and directories, and extended types where extra
135 3.3 Directories
138 Like inodes, directories are packed into compressed metadata blocks, stored
139 in a directory table. Directories are accessed using the start address of
143 Directories are organised in a slightly complex way, and are not simply
147 Directories are therefore organised in a two level list, a directory
[all …]
|
| D | omfs.rst | 12 block sizes from 2k to 8k, with hash-based directories. This
41 dmask=xxx set umask to xxx for directories
69 Files and directories are both represented by omfs_inode::
84 Directories in OMFS are implemented as a large hash table. Filenames are
|
| D | ceph.rst | 23 * Recursive accounting (nested files, directories, bytes)
43 directories, allowing entire directories of dentries and inodes to be
45 extremely large directories can be fragmented and managed by
60 Ceph also provides some recursive accounting on directories for nested
|
| /kernel/linux/linux-4.19/Documentation/arm/Samsung/ |
| D | Overview.txt | 43 several platform directories and then the machine specific directories
47 last in the line of include directories that are processed for the build
61 The old plat-s3c and plat-s5pc1xx directories have been removed, with
64 so many different platform directories.
|
| /kernel/linux/linux-5.10/Documentation/arm/samsung/ |
| D | overview.rst | 46 several platform directories and then the machine specific directories
50 last in the line of include directories that are processed for the build
64 The old plat-s3c and plat-s5pc1xx directories have been removed, with
67 so many different platform directories.
|
| /kernel/linux/linux-5.10/tools/lib/traceevent/Documentation/ |
| D | libtraceevent-plugins.txt | 27 directories. The _tep_ argument is trace event parser context.
28 The plugin directories are :
31 - Directories, specified in _tep_->plugins_dir with priority TEP_PLUGIN_FIRST
37 - Directories, specified in _tep_->plugins_dir with priority TEP_PLUGIN_LAST
55 The _tep_load_plugins_hook_ function walks through all directories with plugins
58 context, passed to _load_plugin()_. Directories and the walk order are the same
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/ |
| D | sysfs-rules.rst | 25 reading directories and opening the files yourself.
54 - all elements of a devpath must be real directories. Symlinks
105 It is planned that all device directories will end up in the tree
111 not contain any device directories themselves, but only flat lists of
115 classification directories into one place at ``/sys/subsystem``,
116 following the layout of the bus directories. All buses and
153 directory does not contain directories for child devices, these links
157 real child device directories in the ``/sys/devices`` tree is a bug in
161 directories live in ``/sys/devices.``
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | sysfs-rules.rst | 25 reading directories and opening the files yourself.
54 - all elements of a devpath must be real directories. Symlinks
105 It is planned that all device directories will end up in the tree
111 not contain any device directories themselves, but only flat lists of
115 classification directories into one place at ``/sys/subsystem``,
116 following the layout of the bus directories. All buses and
153 directory does not contain directories for child devices, these links
157 real child device directories in the ``/sys/devices`` tree is a bug in
161 directories live in ``/sys/devices.``
|
| /kernel/linux/linux-4.19/Documentation/filesystems/caching/ |
| D | cachefiles.txt | 166 Do not create, rename or unlink files and directories in the cache whilst the
175 Do not create files or directories in the cache, lest the cache get confused or
189 directories are culled if not in use.
233 The CacheFiles module will create two directories in the directory it was
248 The module represents index objects as directories with the filename "I..." or
251 Data objects are represented as files if they have no children, or directories
261 Immediately in the representative directory are a collection of directories
276 make a nest of directories, and the last one of which will be the objects
277 inside the last directory. The names of the intermediate directories will have
297 Intermediate directories are always "@" or "+" as appropriate.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/filesystems/caching/ |
| D | cachefiles.rst | 154 Do not create, rename or unlink files and directories in the cache while the
163 Do not create files or directories in the cache, lest the cache get confused or
176 directories are culled if not in use.
213 The CacheFiles module will create two directories in the directory it was
227 The module represents index objects as directories with the filename "I..." or
230 Data objects are represented as files if they have no children, or directories
240 Immediately in the representative directory are a collection of directories
255 make a nest of directories, and the last one of which will be the objects
256 inside the last directory. The names of the intermediate directories will have
278 Intermediate directories are always "@" or "+" as appropriate.
[all …]
|
| /kernel/linux/linux-5.10/fs/squashfs/ |
| D | namei.c | 12 * This file implements code to do filename lookup in directories.
14 * Like inodes, directories are packed into compressed metadata blocks, stored
15 * in a directory table. Directories are accessed using the start address of
19 * Directories are organised in a slightly complex way, and are not simply
23 * Directories are therefore organised in a two level list, a directory
29 * Directories are sorted, and can contain a directory index to speed up
32 * in each metadata block. Directories are sorted in alphabetical order,
|
| /kernel/linux/linux-5.10/fs/hmdfs/ |
| D | Kconfig | 7 the shared directories of the corresponding devices are provided under
8 different device directories; in the merge view, acollection of shared
16 application can access the files and directories under the corresponding
|
| /kernel/linux/linux-4.19/fs/squashfs/ |
| D | namei.c | 25 * This file implements code to do filename lookup in directories.
27 * Like inodes, directories are packed into compressed metadata blocks, stored
28 * in a directory table. Directories are accessed using the start address of
32 * Directories are organised in a slightly complex way, and are not simply
36 * Directories are therefore organised in a two level list, a directory
42 * Directories are sorted, and can contain a directory index to speed up
45 * in each metadata block. Directories are sorted in alphabetical order,
|
| /kernel/linux/linux-4.19/Documentation/arm/ |
| D | README | 59 Several new include directories have been created under include/asm-arm,
61 directories, and their purpose is listed below:
76 used to select which directories and files get included (we will use
79 To this end, we now have arch/arm/mach-$(MACHINE) directories which are
178 classes are given directories - arch/arm/mach-<class> and
180 support the machine class. This directories also contain any machine
|