| /linux/Documentation/filesystems/ext4/ |
| A D | directory.rst | 12 associated with a directory file for the particular directory entry that
83 - Length of this directory entry.
142 - The hash of the directory name
146 - The minor hash of the directory name
187 directory's inode number, the directory's inode generation number, and
189 directory entry.
200 hidden inside the directory file, masquerading as “empty” directory data
229 directory entries.
250 - inode number of this directory.
270 - inode number of parent directory.
[all …]
|
| A 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\_in…
40 for other filesystem features which are not referenced from standard directory
51 - Inode number of lost+found directory.
|
| A 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
|
| /linux/Documentation/filesystems/ |
| A 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
16 1) read access. Locking rules: caller locks directory we are accessing.
37 * check that source is not a directory
54 * If the target exists, lock it. If the source is a non-directory,
85 directory objects, and are acquired in inode pointer order.
96 By (3), any process holding a non-directory lock can only be
104 Any contended object is either held by cross-directory rename or
109 It means that one of the operations is cross-directory rename.
115 Consider the object blocking the cross-directory rename. One
[all …]
|
| A 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
57 directory "b".
[all …]
|
| A D | overlayfs.rst | 121 "upperdir" are combined into a merged directory:
138 directory only. These attributes of the lower directory are hidden.
177 - read part of a directory
178 - remember an offset, and close the directory
179 - re-open the directory some time later
184 directory.
187 underlying directory (upper or lower).
498 found lower directory does not match the stored origin, that directory
499 will not be merged with the upper directory.
515 directory inode.
[all …]
|
| A 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.
239 raw scanning is the directory renaming code.
247 directory of the filesystem, the directory name sometimes shows
281 struct directory { // Short 8.3 names
318 extended slot directory entries as the file name.
320 The C structure for a slot directory entry follows::
[all …]
|
| A D | squashfs.rst | 34 Max entries per directory unlimited unlimited
51 directory data are highly compacted, and packed on byte boundaries. Each
84 | directory |
127 (regular file, directory, device, etc.), the inode contents and length
131 directory inode are defined: inodes optimised for frequently occurring
140 the metablock containing the directory and the offset into the
147 Directories are therefore organised in a two level list, a directory
150 is written once/if the inode start block changes. The directory
151 header/directory entry list is repeated as many times as necessary.
153 Directories are sorted, and can contain a directory index to speed up
[all …]
|
| /linux/Documentation/ABI/testing/ |
| A 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
|
| A D | sysfs-firmware-qemu_fw_cfg | 22 with the file directory), as there is no way to determine the
36 All discoverable blobs listed in the fw_cfg file directory are
50 blob's 'file name' in the fw_cfg directory.
52 directory.
54 fw_cfg directory. This value is the same as used in
55 the parent directory name.
65 convention on the blobs registered in the file directory,
85 "basename", as illustrated below (assume current directory is
93 Construction of the directory tree and symlinks is done on a
102 under the /sys/firmware/qemu_fw_cfg/by_key directory.
|
| A 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
|
| A D | sysfs-kernel-livepatch | 8 The /sys/kernel/livepatch directory contains subdirectories for
16 The patch directory contains subdirectories for each kernel
55 The object directory contains subdirectories for each function
63 The function directory contains attributes regarding the
66 The directory name contains the patched function name and a
|
| A 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.
|
| /linux/Documentation/PCI/endpoint/ |
| A 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>.
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
108 The <EPC Device> directory will have a list of symbolic links to
[all …]
|
| /linux/Documentation/driver-api/driver-model/ |
| A 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.
|
| A 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/scripts/clang-tools/ |
| A D | gen_compile_commands.py | 67 os.path.abspath(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):
202 log_level, directory, output, ar, paths = parse_arguments()
233 entry = process_line(directory, result.group(1),
|
| /linux/tools/perf/Documentation/ |
| A 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/Documentation/usb/ |
| A D | gadget-testing.rst | 40 The function name to use when creating the function directory is "acm".
41 The ACM function provides just one attribute in its function directory:
79 The function name to use when creating the function directory is "ecm".
80 The ECM function provides these attributes in its function directory:
160 The EEM function provides these attributes in its function directory:
200 The function directory is intentionally empty and not modifiable.
224 The HID function provides these attributes in its function directory:
297 The MASS STORAGE function provides these attributes in its directory:
309 and a default lun.0 directory corresponding to SCSI LUN #0.
321 In each lun directory there are the following attribute files:
[all …]
|
| /linux/drivers/gpu/drm/i915/gt/shaders/ |
| A 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/Documentation/filesystems/spufs/ |
| A 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/drivers/infiniband/hw/hfi1/ |
| A 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()
|
| /linux/Documentation/networking/ |
| A 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/Documentation/devicetree/bindings/net/ |
| A D | socionext-netsec.txt | 11 - phy-mode: See ethernet.txt file in the same directory
12 - phy-handle: See ethernet.txt in the same directory.
26 Optional properties: (See ethernet.txt file in the same directory)
29 - max-speed: See ethernet.txt in the same directory.
30 - max-frame-size: See ethernet.txt in the same directory.
|
| /linux/Documentation/i2c/ |
| A D | i2c-sysfs.rst | 40 There is a list of symbolic links under that directory. The links that
66 controllers. Linux kernel has I2C bus drivers under source directory
129 | |-- 73-0040 (I2C sensor device with hwmon directory)
146 in logical I2C bus directory which is fanned out from another I2C bus.
157 ls: /sys/bus/i2c/devices/i2c-7/mux_device: No such file or directory
196 First of all, let us go to the directory of ``i2c-7``::
220 Let us continue the journey to directory ``i2c-73`` in either ways::
319 Inside each I2C device directory, there is a file named ``name``.
343 ls: 73-0070/driver: No such file or directory
349 device, we may have different content in the device directory.
[all …]
|