| /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 …]
|
| D | sysfs-class | 7 in the kernel. The individual directories will consist
9 directories.
|
| D | sysfs-devices-power_resources_D0 | 9 If present, it contains symbolic links to device directories
12 of the links are the same as the names of the directories they
|
| D | sysfs-devices-power_resources_wakeup | 9 If present, it contains symbolic links to device directories
12 the links are the same as the names of the directories they
|
| D | sysfs-devices-power_resources_D2 | 10 If present, it contains symbolic links to device directories
13 of the links are the same as the names of the directories they
|
| D | sysfs-devices-power_resources_D3hot | 10 If present, it contains symbolic links to device directories
13 names of the links are the same as the names of the directories
|
| D | sysfs-devices-power_resources_D1 | 10 If present, it contains symbolic links to device directories
13 of the links are the same as the names of the directories they
|
| /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
|
| D | hpfs.rst | 167 You encounter this problem only if you have many directories so that
172 You can't delete open directories.
174 You can't rename over directories (what is it good for?).
184 (lost files, unbalanced directories). (I guess all filesystem may do it).
198 probably because of directories created with old version of this driver.
207 When you have two (or more) lost directories pointing each to other, chkdsk
285 Directories have no longer archive attribute set (some programs don't like
294 error sometimes when opening directories in PMSHELL)
|
| D | zonefs.rst | 62 by sub-directories. This file structure is built entirely using zone information
82 Zone type sub-directories
96 These two directories are the only directories that exist in zonefs. Users
97 cannot create other directories and cannot rename nor delete the "cnv" and
98 "seq" sub-directories.
100 The size of the directories indicated by the st_size field of struct stat,
108 of zones of a particular type. That is, both the "cnv" and "seq" directories
117 sub-directories is not allowed.
368 The size of the zone files sub-directories indicate the number of files
|
| D | fscrypt.rst | 9 transparent encryption of files and directories.
46 userspace provides the key, all regular files, directories, and
124 encrypted files and directories before removing a master key, as
169 policies on all new encrypted directories.
322 For directories that are indexed using a secret-keyed dirhash over the
327 encrypted directories use this style of hashing.
471 For new encrypted directories, use v2 policies.
520 files, directories (recursively), and symlinks created in the
528 regular files and directories, including nonempty directories.
664 On encrypted files and directories it gets the inode's 16-byte nonce.
[all …]
|
| /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-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-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-5.10/Documentation/arm/ |
| D | arm.rst | 66 Several new include directories have been created under include/asm-arm,
68 directories, and their purpose is listed below:
85 used to select which directories and files get included (we will use
88 To this end, we now have arch/arm/mach-$(MACHINE) directories which are
187 classes are given directories - arch/arm/mach-<class> - which contain
|
| /kernel/uniproton/cmake/functions/ |
| D | uniproton_functions.cmake | 46 # @cppincs List[str]: the include directories path of list
86 # @cppincs List[str]: the include directories path of list
127 # @cppincs List[str]: the include directories path of list
152 # @cppincs List[str]: the include directories path of list
|
| /kernel/linux/linux-5.10/fs/jffs2/ |
| D | build.c | 66 /* we can get high latency here with huge directories */ in jffs2_build_inode_pass1()
81 /* If we appear (at this stage) to have hard-linked directories, in jffs2_build_inode_pass1()
133 they were directories, then decrement the nlink of their in jffs2_build_filesystem()
165 * dead directories which still had some old dirents lying in jffs2_build_filesystem()
183 * directories during fs build, so set it to the in jffs2_build_filesystem()
196 /* We clear ic->pino_nlink ∀ directories' ic *only* if dir_hardlinks in jffs2_build_filesystem()
206 /* For directories, ic->pino_nlink holds that parent inode # */ in jffs2_build_filesystem()
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| D | gadget_configfs.rst | 97 directories must be created:
239 Remove strings directories in configurations:
275 Remove strings directories in the gadget::
299 In configfs there are items and groups, both represented as directories.
303 The user can create and remove directories, but cannot remove files,
353 the directories in general can be named at will. A group can have
|