Searched full:directory (Results 1 – 25 of 683) sorted by relevance
12345678910>>...28
| /Documentation/filesystems/ext4/ |
| D | directory.rst | 3 Directory Entries
6 In an ext4 filesystem, a directory is more or less a flat file that maps
8 filesystem. There can be many directory entries across the filesystem
11 such, directory entries are found by reading the data block(s)
12 associated with a directory file for the particular directory entry that
18 By default, each directory lists its entries in an “almost-linear”
20 sense because directory entries are not split across filesystem blocks.
21 Therefore, it is more accurate to say that a directory is a series of
22 data blocks and that each block contains a linear array of directory
26 directory is of course signified by reaching the end of the file. Unused
[all …]
|
| D | special_inodes.rst | 19 - Root directory.
27 - Undelete directory.
37 …- Traditional first non-reserved inode. Usually this is the lost+found directory. See s_first_ino …
40 for other filesystem features which are not referenced from standard directory
51 - Inode number of lost+found directory.
|
| D | allocators.rst | 38 The fourth trick is that all the inodes in a directory are placed in the
39 same block group as the directory, when feasible. The working assumption
40 here is that all the files in a directory might be related, therefore it
46 directory is created in the root directory, the inode allocator scans
47 the block groups and puts that directory into the least heavily loaded
49 over a disk; as the top-level directory/file blobs fill up one block
|
| D | inlinedata.rst | 29 directory. Following that is a 56-byte space for an array of directory
33 i_block and EA space are treated as separate dirent blocks; directory
36 Inline directory entries are not checksummed, as the inode checksum
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 2 Directory Locking
6 Locking scheme used for directory operations is based on two
10 When taking the i_rwsem on multiple non-directory objects, we
22 * lock the directory we are accessing (shared)
26 * lock the directory we are accessing (exclusive)
37 * check that the source is not a directory
40 5. rename that is _not_ cross-directory. Locking rules:
45 The source needs to be locked if it's a non-directory, target - if it's
46 a non-directory or about to be removed.
50 otherwise and the target because mixing directory and non-directory is
[all …]
|
| D | dnotify.rst | 4 Linux Directory Notification
9 The intention of directory notification is to allow user applications
10 to be notified when a directory, or any of the files in it, are changed.
12 on a directory using a fcntl(2) call and the notifications themselves
19 DN_ACCESS A file in the directory was accessed (read)
20 DN_MODIFY A file in the directory was modified (write,truncate)
21 DN_CREATE A file was created in the directory
22 DN_DELETE A file was unlinked from directory
23 DN_RENAME A file in the directory was renamed
24 DN_ATTRIB A file in the directory had its attributes
[all …]
|
| D | overlayfs.rst | 26 non-directory objects may report an st_dev from the lower filesystem or
29 over the lifetime of a non-directory object. Many applications and
92 It would be more correct to refer to an upper and lower 'directory
94 directory trees to be in the same filesystem and there is no
113 upper and lower filesystems and refers to a non-directory in either,
117 Where both upper and lower objects are directories, a merged directory
121 "upperdir" are combined into a merged directory::
126 The "workdir" needs to be an empty directory on the same filesystem
129 Then whenever a lookup is requested in such a merged directory, the
130 lookup is performed in each actual directory and the combined result
[all …]
|
| D | vfat.rst | 32 The permission mask for the directory.
47 The default is set from dmask option. If the directory is
99 currently exist in the directory, longfile.txt will
177 the ATTR_RO of the directory will just be ignored,
182 the directory, set this option.
198 **stale_rw**: This option maintains an index (cache) of directory
205 on the on-disk location of a file in the MS-DOS directory entry.
238 a get next directory entry approach. The only thing left that uses
239 raw scanning is the directory renaming code.
246 - When a volume name is the same as a directory name in the root
[all …]
|
| D | autofs.rst | 52 directory should be a mount trap is based on a master map. This master
58 mount is considered to be *indirect*), then the root directory is
59 always a regular directory, otherwise it is a mount trap when it is
60 empty and a regular directory when not empty. Note that *direct* and
62 directory is a mount trap only if the filesystem is mounted *direct*
65 Directories created in the root directory are mount traps only if the
84 which are provided by the Linux VFS. Any directory provided by a
92 (potentially) a mount trap. Any access to this directory beyond a
95 should be mounted on the directory and to return it. The VFS is
97 directory.
[all …]
|
| D | squashfs.rst | 34 Max entries per directory unlimited unlimited
37 Directory indexes yes no
51 directory data are highly compacted, and packed on byte boundaries. Each
53 file type, i.e. regular file, directory, symbolic link, and block/char device
144 | directory |
161 the source directory, and checked for duplicates. Once all file data has been
162 written the completed inode, directory, fragment, export, uid/gid lookup and
187 (regular file, directory, device, etc.), the inode contents and length
191 directory inode are defined: inodes optimised for frequently occurring
199 in a directory table. Directories are accessed using the start address of
[all …]
|
| /Documentation/PCI/endpoint/ |
| D | pci-endpoint-cfs.rst | 17 The PCI Endpoint Core layer creates pci_ep directory in the mounted configfs
18 directory. configfs can be mounted using the following command::
22 Directory Structure
27 the *controllers* directory and every EPF driver present in the system
28 will have an entry in the *functions* directory.
38 Every registered EPF driver will be listed in controllers directory. The
52 user has to create a directory inside <EPF DriverN>.
54 Every <EPF device> directory consists of the following entries that can be
80 interface should be added in 'primary' directory and symlink of endpoint
82 directory.
[all …]
|
| /Documentation/ABI/testing/ |
| D | configfs-iio | 7 directory. It contains sub-groups corresponding to IIO
14 Industrial IO software triggers directory.
20 High resolution timers directory. Creating a directory here
27 Industrial IO software devices directory.
33 Dummy IIO devices directory. Creating a directory here will result
|
| D | debugfs-vfio | 5 Description: This debugfs file directory is used for debugging
6 of vfio devices, it's a common directory for all vfio devices.
8 directory.
14 Description: This debugfs file directory is used for debugging
17 could be created under this directory.
|
| D | sysfs-firmware-qemu_fw_cfg | 23 with the file directory), as there is no way to determine the
37 All discoverable blobs listed in the fw_cfg file directory are
51 blob's 'file name' in the fw_cfg directory.
53 directory.
55 fw_cfg directory. This value is the same as used in
56 the parent directory name.
66 convention on the blobs registered in the file directory,
86 "basename", as illustrated below (assume current directory is
94 Construction of the directory tree and symlinks is done on a
103 under the /sys/firmware/qemu_fw_cfg/by_key directory.
|
| D | sysfs-firmware-opal-powercap | 4 Description: Powercap directory for Powernv (P8, P9) servers
6 Each folder in this directory contains a
15 Description: System powercap directory and attributes applicable for
18 This directory provides powercap information. It
|
| D | sysfs-devices-software_node | 5 This directory contains the details about the device that are
7 firmware_node directory which contains the details that are
9 directory will show the properties the device has, and the
|
| D | sysfs-ibft | 4 Description: The /sys/firmware/ibft/initiator directory will contain
11 Description: The /sys/firmware/ibft/targetX directory will contain
21 Description: The /sys/firmware/ibft/ethernetX directory will contain
28 Description: The /sys/firmware/ibft/acpi_header directory will contain files
|
| D | sysfs-firmware-sgi_uv | 5 The /sys/firmware/sgi_uv directory contains information
8 Under that directory are a number of read-only attributes::
50 The /sys/firmware/sgi_uv directory also contains two directories::
55 The hubs directory contains a number of hub objects, each representing
59 Each hub object directory contains a number of read-only attributes::
94 Each hub object directory also contains a number of port objects,
99 Each port object directory contains a number of read-only attributes::
124 The pcibuses directory contains a number of PCI bus objects.
|
| D | sysfs-bus-vfio-mdev | 5 This directory contains list of directories of currently
9 Each supported type is a directory whose name is created
17 This directory gives details of supported type, like name,
40 This directory contains symbolic links pointing to mdev
93 This directory represents device directory of mediated
102 directory of which this mediated device is created.
|
| D | sysfs-kernel-livepatch | 8 The /sys/kernel/livepatch directory contains subdirectories for
16 The patch directory contains subdirectories for each kernel
63 The object directory contains subdirectories for each function
79 The function directory contains attributes regarding the
82 The directory name contains the patched function name and a
|
| /Documentation/driver-api/driver-model/ |
| D | binding.rst | 63 A symlink is created in the bus's 'devices' directory that points to
64 the device's directory in the physical hierarchy.
66 A symlink is created in the driver's 'devices' directory that points
67 to the device's directory in the physical hierarchy.
69 A directory for the device is created in the class's directory. A
70 symlink is created in that directory that points to the device's
74 physical directory to either its class directory, or the class's
75 top-level directory. One can also be created to point to its driver's
76 directory also.
|
| D | bus.rst | 89 There is a top-level directory named 'bus'.
91 Each bus gets a directory in the bus directory, along with two default
98 Drivers registered with the bus get a directory in the bus's drivers
99 directory::
110 the bus's devices directory to the device's directory in the physical
143 sysfs directory using::
|
| /Documentation/admin-guide/mm/damon/ |
| D | usage.rst | 42 creates multiple directories and files under its sysfs directory,
44 from the files under the directory.
61 directory is having ``/`` suffix, and files in each directory are separated by
107 has one directory named ``admin``. The directory contains the files for
109 having the root permission could use this directory.
116 Under the ``admin`` directory, one directory, ``kdamonds``, which has files for
119 details) exists. In the beginning, this directory has only one file,
121 child directories named ``0`` to ``N-1``. Each directory represents each
129 In each kdamond directory, two files (``state`` and ``pid``) and one directory
147 action tried regions directory for each DAMON-based operation scheme of the
[all …]
|
| /Documentation/networking/ |
| D | sysfs-tagging.rst | 12 the same directory, ouch!
16 sysfs, sysfs now has tagging directory support.
19 the sysfs directory entries we ensure that we don't have conflicts
23 Each sysfs directory entry may be tagged with a namespace via the
24 ``void *ns member`` of its ``kernfs_node``. If a directory entry is tagged,
|
| /Documentation/filesystems/spufs/ |
| D | spu_create.rst | 28 point to a non-existing directory in the mount point of the SPU file
29 system (spufs). When spu_create is successful, a directory gets cre-
34 ated directory entries in spufs are removed. When the last file handle
35 pointing either inside of the context directory or to this file
47 directory in spufs. mode is modified with the user's umask(2) value
48 and then used for both the directory and the files contained in it. The
72 EINVAL pathname is not a directory in the spufs mount point.
96 A part of pathname is not a directory.
|
12345678910>>...28