| /linux-6.12.1/Documentation/filesystems/ext4/ |
| D | directory.rst | 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
27 directory entries are signified by inode = 0. By default the filesystem
[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.
|
| /linux-6.12.1/Documentation/filesystems/ |
| D | directory-locking.rst | 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
53 6. cross-directory rename. The trickiest in the whole bunch. Locking rules:
[all …]
|
| D | dnotify.rst | 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
36 file descriptor associated with the directory in which the event occurred.
[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 | squashfs.rst | 34 Max entries per directory unlimited unlimited
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
200 the metablock containing the directory and the offset into the
[all …]
|
| /linux-6.12.1/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
|
| /linux-6.12.1/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::
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.
84 The <EPF Device> directory can have a list of symbolic links
[all …]
|
| /linux-6.12.1/tools/power/cpupower/ |
| D | README | 29 default directory
32 In the case of default directory, build and install process requires no
40 The output directory for the 'make' command is the current directory and
66 custom directory
71 'O' - build directory
72 'DESTDIR' - installation directory. This variable could also be setup in
96 build directory is the current one, build everything there and install
116 regardles of the root output directory.
124 installation directory
126 default directory
[all …]
|
| /linux-6.12.1/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 …]
|
| /linux-6.12.1/tools/perf/Documentation/ |
| D | perf.data-directory-format.txt | 1 perf.data directory format
5 disclaimer once the directory format soaks in.
8 This document describes the on-disk perf.data directory format.
20 - there is a single perf.data file named 'data' within the directory.
30 Currently the only 'perf record' option to output to a directory is
31 the --kcore option which puts a copy of /proc/kcore into the directory.
46 1 directory, 4 files
|
| /linux-6.12.1/scripts/clang-tools/ |
| D | gen_compile_commands.py | 67 os.path.realpath(args.directory),
70 args.paths if len(args.paths) > 0 else [args.directory])
73 def cmdfiles_in_dir(directory): argument
86 exclude_dirs = [ os.path.join(directory, d) for d in _EXCLUDE_DIRS ]
88 for dirpath, dirnames, filenames in os.walk(directory, topdown=True):
188 log_level, directory, output, ar, paths = parse_arguments()
216 entry = process_line(directory, result.group('command_prefix'),
|
| /linux-6.12.1/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::
|
| /linux-6.12.1/drivers/gpu/drm/i915/gt/shaders/ |
| D | README | 9 i915/gt/shaders/clear_kernel directory.
25 "-Ddri-drivers=i965", and run this script from IGT source root directory"
28 * IGT gpu tools source code is located on your home directory (~) as ~/igt
29 * Mesa source code is located on your home directory (~) as ~/mesa
30 and built under the ~/mesa/build directory
31 * Linux kernel source code is under your home directory (~) as ~/linux
|
| /linux-6.12.1/Documentation/usb/ |
| D | gadget-testing.rst | 41 The function name to use when creating the function directory is "acm".
42 The ACM function provides just one attribute in its function directory:
80 The function name to use when creating the function directory is "ecm".
81 The ECM function provides these attributes in its function directory:
120 The function name to use when creating the function directory is "geth".
121 The ECM subset function provides these attributes in its function directory:
160 The function name to use when creating the function directory is "eem".
161 The EEM function provides these attributes in its function directory:
200 The function name to use when creating the function directory is "ffs".
201 The function directory is intentionally empty and not modifiable.
[all …]
|
| /linux-6.12.1/samples/bpf/ |
| D | README.rst | 4 This directory contains a test stubs, verifier test-suite and examples
7 Note that the XDP-specific samples have been removed from this directory and
9 See the commit messages removing each tool from this directory for how to
50 This will create a local "usr/include" directory in the git/build top
51 level directory, that the make system will automatically pick up first.
57 top level directory::
61 It is also possible to call make from this directory. This will just
107 sync (not necessarily and it creates a local "usr/include" directory also)::
|
| /linux-6.12.1/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.
|
| /linux-6.12.1/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,
|
| /linux-6.12.1/drivers/infiniband/hw/hfi1/ |
| D | eprom.c | 253 void *directory, void **data, u32 *size) in read_segment_platform_config() argument
267 (directory + EP_PAGE_SIZE - sizeof(*footer)); in read_segment_platform_config()
287 (directory + EP_PAGE_SIZE - directory_size); in read_segment_platform_config()
423 u32 directory[EP_PAGE_DWORDS]; /* aligned buffer */ in eprom_read_platform_config() local
434 ret = read_length(dd, SEG_SIZE - EP_PAGE_SIZE, EP_PAGE_SIZE, directory); in eprom_read_platform_config()
439 if (directory[EP_PAGE_DWORDS - 1] == FOOTER_MAGIC) { in eprom_read_platform_config()
441 ret = read_segment_platform_config(dd, directory, data, size); in eprom_read_platform_config()
|