Home
last modified time | relevance | path

Searched refs:directory (Results 1 – 25 of 987) sorted by relevance

12345678910>>...40

/Linux-v5.4/Documentation/filesystems/ext4/
Ddirectory.rst6 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 …]
Dspecial_inodes.rst19 - Root directory.
27 - Undelete directory.
37 …- Traditional first non-reserved inode. Usually this is the lost+found directory. See s\_first\_in…
/Linux-v5.4/Documentation/filesystems/
Ddirectory-locking.rst6 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.
25 4) rename() that is _not_ cross-directory. Locking rules: caller locks
28 if the target already exists, lock it. If the source is a non-directory,
37 * check that source is not a directory
43 6) cross-directory rename. The trickiest in the whole bunch. Locking
54 * If the target exists, lock it. If the source is a non-directory,
65 If no directory is its own ancestor, the scheme above is deadlock-free.
74 (1) if object removal or non-cross-directory rename holds lock on A and
[all …]
Ddnotify.txt6 The intention of directory notification is to allow user applications
7 to be notified when a directory, or any of the files in it, are changed.
9 on a directory using a fcntl(2) call and the notifications themselves
15 DN_ACCESS A file in the directory was accessed (read)
16 DN_MODIFY A file in the directory was modified (write,truncate)
17 DN_CREATE A file was created in the directory
18 DN_DELETE A file was unlinked from directory
19 DN_RENAME A file in the directory was renamed
20 DN_ATTRIB A file in the directory had its attributes
31 file descriptor associated with the directory in which the event occurred.
[all …]
Doverlayfs.txt24 non-directory objects may report an st_dev from the lower filesystem or
27 over the lifetime of a non-directory object. Many applications and
59 It would be more correct to refer to an upper and lower 'directory
61 directory trees to be in the same filesystem and there is no
78 upper and lower filesystems and refers to a non-directory in either,
82 Where both upper and lower objects are directories, a merged directory
86 "upperdir" are combined into a merged directory:
91 The "workdir" needs to be an empty directory on the same filesystem
94 Then whenever a lookup is requested in such a merged directory, the
95 lookup is performed in each actual directory and the combined result
[all …]
Dvfat.txt20 dmask=### -- The permission mask for the directory.
32 The default is set from `dmask' option. (If the directory is
79 currently exist in the directory, 'longfile.txt' will
138 the ATTR_RO of the directory will just be ignored,
143 the directory, set this option.
158 stale_rw: This option maintains an index (cache) of directory
165 on the on-disk location of a file in the MS-DOS directory entry.
197 a get next directory entry approach. The only thing left that uses
198 raw scanning is the directory renaming code.
204 * When a volume name is the same as a directory name in the root
[all …]
Dsquashfs.txt29 Max entries per directory: unlimited unlimited
45 directory data are highly compacted, and packed on byte boundaries. Each
47 file type, i.e. regular file, directory, symbolic link, and block/char device
78 | directory |
95 the source directory, and checked for duplicates. Once all file data has been
96 written the completed inode, directory, fragment, export, uid/gid lookup and
121 (regular file, directory, device, etc.), the inode contents and length
125 directory inode are defined: inodes optimised for frequently occurring
133 in a directory table. Directories are accessed using the start address of
134 the metablock containing the directory and the offset into the
[all …]
Dsysfs-tagging.txt9 the same directory, ouch!
13 sysfs, sysfs now has tagging directory support.
16 the sysfs directory entries we ensure that we don't have conflicts
20 Each sysfs directory entry may be tagged with a namespace via the
21 void *ns member of its kernfs_node. If a directory entry is tagged,
/Linux-v5.4/scripts/
Dgen_compile_commands.py61 directory = args.directory or os.getcwd()
62 output = args.output or os.path.join(directory, _DEFAULT_OUTPUT)
63 directory = os.path.abspath(directory)
65 return log_level, directory, output
112 log_level, directory, output = parse_arguments()
121 for dirpath, _, filenames in os.walk(directory):
134 entry = process_line(directory, dirpath,
/Linux-v5.4/Documentation/ABI/testing/
Dconfigfs-iio7 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
Dsysfs-firmware-qemu_fw_cfg22 with the file directory), as there is no way to determine the
36 All discoverable blobs listed in the fw_cfg file directory are
49 blob's 'file name' in the fw_cfg directory.
51 directory.
53 fw_cfg directory. This value is the same as used in
54 the parent directory name.
63 convention on the blobs registered in the file directory,
83 "basename", as illustrated below (assume current directory is
91 Construction of the directory tree and symlinks is done on a
100 under the /sys/firmware/qemu_fw_cfg/by_key directory.
Dsysfs-firmware-opal-powercap4 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
Dsysfs-devices-software_node5 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
Dsysfs-kernel-livepatch8 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
Dsysfs-bus-vfio-mdev5 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,
39 This directory contains symbolic links pointing to mdev
92 This directory represents device directory of mediated
101 directory of which this mediated device is created.
/Linux-v5.4/Documentation/PCI/endpoint/
Dpci-endpoint-cfs.rst17 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 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
51 user has to create a directory inside <EPF DriverN>.
53 Every <EPF device> directory consists of the following entries that can be
75 Every registered EPC device will be listed in controllers directory. The
89 The <EPC Device> directory will have a list of symbolic links to
93 The <EPC Device> directory will also have a *start* field. Once
/Linux-v5.4/Documentation/driver-api/driver-model/
Dbinding.rst63 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.
Dclass.rst79 sysfs directory structure
81 There is a top-level sysfs directory named 'class'.
83 Each class gets a directory in the class directory, along with two
92 Drivers registered with the class get a symlink in the drivers/ directory
93 that points to the driver's directory (under its bus directory)::
102 Each device gets a symlink in the devices/ directory that points to the
103 device's directory in the physical hierarchy::
134 sysfs directory using::
140 class's directory in sysfs.
Dbus.rst89 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-v5.4/Documentation/usb/
Dgadget-testing.rst40 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:
119 The function name to use when creating the function directory is "geth".
120 The ECM subset function provides these attributes in its function directory:
159 The function name to use when creating the function directory is "eem".
160 The EEM function provides these attributes in its function directory:
199 The function name to use when creating the function directory is "ffs".
200 The function directory is intentionally empty and not modifiable.
[all …]
/Linux-v5.4/samples/bpf/
DREADME.rst4 This directory contains a test stubs, verifier test-suite and examples
26 This will creates a local "usr/include" directory in the git/build top
27 level directory, that the make system automatically pickup first.
33 top level directory::
37 Do notice the "/" slash after the directory name.
39 It is also possible to call make from this directory. This will just
/Linux-v5.4/Documentation/devicetree/bindings/net/
Dsocionext-netsec.txt11 - 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-v5.4/Documentation/x86/
Dintel_mpx.rst42 2) That setup code allocates (virtual) space for the "bounds directory",
43 points the "bndcfgu" register to the directory (must also set the valid
53 succeed, and notes the location of the bounds directory. Userspace is
54 expected to keep the bounds directory at that location. We note it
56 to access the bounds directory register is an expensive operation.
58 issues a bndstx instruction. Since the bounds directory is empty at
61 in the bounds directory point to the new table.
68 the table and remove the entry in the directory.
77 * allocates virtual space for the bounds directory (malloc() essentially)
78 * points the hardware BNDCFGU register at the directory
[all …]
/Linux-v5.4/drivers/infiniband/hw/hfi1/
Deprom.c294 void *directory, void **data, u32 *size) in read_segment_platform_config() argument
308 (directory + EP_PAGE_SIZE - sizeof(*footer)); in read_segment_platform_config()
328 (directory + EP_PAGE_SIZE - directory_size); in read_segment_platform_config()
464 u32 directory[EP_PAGE_DWORDS]; /* aligned buffer */ in eprom_read_platform_config() local
475 ret = read_length(dd, SEG_SIZE - EP_PAGE_SIZE, EP_PAGE_SIZE, directory); in eprom_read_platform_config()
480 if (directory[EP_PAGE_DWORDS - 1] == FOOTER_MAGIC) { in eprom_read_platform_config()
482 ret = read_segment_platform_config(dd, directory, data, size); in eprom_read_platform_config()
/Linux-v5.4/tools/lib/traceevent/Documentation/
Dlibtraceevent-set_flag.txt32 directory. This directory is defined at library compile
36 - in system's plugin directory
37 - in directory, defined by the environment variable _TRACEEVENT_PLUGIN_DIR_
38 - in user's home directory, _~/.traceevent/plugins_

12345678910>>...40