Searched full:directory (Results 1 – 25 of 770) sorted by relevance
12345678910>>...31
| /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 | 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
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.
[all …]
|
| D | overlayfs.txt | 24 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 …]
|
| D | dnotify.txt | 1 Linux Directory Notification
6 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
[all …]
|
| D | squashfs.txt | 29 Max entries per directory: unlimited unlimited
32 Directory indexes: yes no
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
[all …]
|
| D | sysfs-tagging.txt | 9 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,
|
| D | vfat.txt | 20 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 …]
|
| D | autofs.txt | 55 directory should be a mount trap or not is quite _ad hoc_, largely for
60 mount is considered to be *indirect*), then the root directory is
61 always a regular directory, otherwise it is a mount trap when it is
62 empty and a regular directory when not empty. Note that *direct* and
64 directory is a mount trap only if the filesystem is mounted *direct*
67 Directories created in the root directory are mount traps only if the
86 which are provided by the Linux VFS. Any directory provided by a
94 (potentially) a mount trap. Any access to this directory beyond a
97 should be mounted on the directory and to return it. The VFS is
99 directory.
[all …]
|
| D | hpfs.txt | 98 moved ... sometimes it works. But the link is partly stored in directory
115 Czech OS/2 another file in that directory, that file was inaccessible too. OS/2
117 (note, that files in HPFS directory must be sorted) and when searching for
118 a file. Finally when I opened this directory in PmShell, PmShell crashed (the
119 funny thing was that, when rebooted, PmShell tried to reopen this directory
147 (returning error ENOSPC). That's because file in non-leaf node in directory tree
148 (one directory, if it's large, has dirents in tree on HPFS) must be replaced
150 the old one so the new name doesn't fit in directory node (dnode). And that
151 would result in directory tree splitting, that takes disk space. Workaround is
155 preallocated directory band is full i.e.
[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 | 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
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.
|
| 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-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
|
| 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,
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.
|
| /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 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
[all …]
|
| /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 | class.rst | 79 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.
|
| 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/x86/ |
| D | intel_mpx.rst | 42 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 …]
|
| /Documentation/devicetree/bindings/net/ |
| 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.
|
| /Documentation/sh/ |
| D | new-machine.txt | 12 1. New Directory Structure
15 The first thing to note is the new directory structure. Under 2.4, most
19 companion chip type, and CPU type. Looking at a tree view of this directory
92 In the first case, this is just a matter of making a directory for your
95 it makes more sense to have a common top-level arch/sh/boards/ directory
99 After you have setup your new arch/sh/boards/ directory, remember that you
100 should also add a directory in include/asm-sh for headers localized to this
102 seamlessly with the build system, it's best to have this directory the same
103 as the arch/sh/boards/ directory name, though if your board is again part of
105 overloading), and you can feel free to name the directory after the family
[all …]
|
12345678910>>...31