| /Linux-v4.19/Documentation/ |
| D | 00-INDEX | 28 - directory with info on customizing EDID for broken gfx/displays.
44 - directory with info on RCU (read-copy update).
60 - directory with info about Linux on the ARM architecture.
62 - directory with info about Linux on the 64 bit ARM architecture.
66 - directory with info on controlling backlights in flat panel displays
76 - directory with info on TI GPMC (General Purpose Memory Controller)
80 - directory with information on the CD-ROM drivers that Linux has.
106 - directory with info on the Crypto API.
116 - directory with info on development tools for the kernel.
118 - directory with info on Device Mapper.
[all …]
|
| /Linux-v4.19/Documentation/filesystems/ext4/ondisk/ |
| 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\_in…
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | directory-locking | 1 Locking scheme used for directory operations is based on two
5 When taking the i_rwsem on multiple non-directory objects, we
11 1) read access. Locking rules: caller locks directory we are accessing.
20 4) rename() that is _not_ cross-directory. Locking rules: caller locks
23 if the target already exists, lock it. If the source is a non-directory,
31 * check that source is not a directory
36 6) cross-directory rename. The trickiest in the whole bunch. Locking
46 * If the target exists, lock it. If the source is a non-directory,
56 If no directory is its own ancestor, the scheme above is deadlock-free.
64 (1) if object removal or non-cross-directory rename holds lock on A and
[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 | 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
31 file descriptor associated with the directory in which the event occurred.
[all …]
|
| 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 | fscrypt.rst | 45 supports marking an empty directory as encrypted. Then, after
47 symbolic links created in that directory tree are transparently
113 Each encrypted directory tree is protected by a *master key*. Master
121 To "unlock" an encrypted directory tree, userspace must provide the
123 of which protects any number of directory trees on any number of
137 each regular file, directory, and symbolic link. This has several
152 reused out of necessity. With a unique key per directory, IV reuse
153 is limited to within a single directory.
189 directory trees are permitted to use different encryption modes.
224 requirements to retain support for efficient directory lookups and
[all …]
|
| D | squashfs.txt | 29 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 …]
|
| 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,
|
| /Linux-v4.19/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-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
|
| /Linux-v4.19/Documentation/PCI/endpoint/ |
| D | pci-endpoint-cfs.txt | 11 The PCI Endpoint Core layer creates pci_ep directory in the mounted configfs
12 directory. configfs can be mounted using the following command.
20 the *controllers* directory and and every EPF driver present in the system
21 will have an entry in the *functions* directory.
29 Every registered EPF driver will be listed in controllers directory. The
41 user has to create a directory inside <EPF DriverN>.
43 Every <EPF device> directory consists of the following entries that can be
63 Every registered EPC device will be listed in controllers directory. The
76 The <EPC Device> directory will have a list of symbolic links to
80 The <EPC Device> directory will also have a *start* field. Once
|
| /Linux-v4.19/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 - local-mac-address: See ethernet.txt in the same directory.
30 - mac-address: See ethernet.txt in the same directory.
31 - max-speed: See ethernet.txt in the same directory.
32 - max-frame-size: See ethernet.txt in the same directory.
|
| /Linux-v4.19/sound/xen/ |
| D | xen_snd_front_shbuf.c | 41 kfree(buf->directory); in xen_snd_front_shbuf_free()
61 ptr = buf->directory; in fill_page_dir()
112 frame = xen_page_to_gfn(virt_to_page(buf->directory + in grant_references()
148 buf->directory = kcalloc(num_pages_dir, XEN_PAGE_SIZE, GFP_KERNEL); in alloc_int_buffers()
149 if (!buf->directory) in alloc_int_buffers()
162 kfree(buf->directory); in alloc_int_buffers()
163 buf->directory = NULL; in alloc_int_buffers()
|
| /Linux-v4.19/Documentation/driver-model/ |
| D | binding.txt | 62 A symlink is created in the bus's 'devices' directory that points to
63 the device's directory in the physical hierarchy.
65 A symlink is created in the driver's 'devices' directory that points
66 to the device's directory in the physical hierarchy.
68 A directory for the device is created in the class's directory. A
69 symlink is created in that directory that points to the device's
73 physical directory to either its class directory, or the class's
74 top-level directory. One can also be created to point to its driver's
75 directory also.
|
| D | class.txt | 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:
131 sysfs directory using:
137 class's directory in sysfs.
|
| D | bus.txt | 87 There is a top-level directory named 'bus'.
89 Each bus gets a directory in the bus directory, along with two default
96 Drivers registered with the bus get a directory in the bus's drivers
97 directory:
108 the bus's devices directory to the device's directory in the physical
138 sysfs directory using:
|
| /Linux-v4.19/Documentation/usb/ |
| D | gadget-testing.txt | 34 The function name to use when creating the function directory is "acm".
35 The ACM function provides just one attribute in its function directory:
63 The function name to use when creating the function directory is "ecm".
64 The ECM function provides these attributes in its function directory:
96 The function name to use when creating the function directory is "geth".
97 The ECM subset function provides these attributes in its function directory:
129 The function name to use when creating the function directory is "eem".
130 The EEM function provides these attributes in its function directory:
162 The function name to use when creating the function directory is "ffs".
163 The function directory is intentionally empty and not modifiable.
[all …]
|
| /Linux-v4.19/samples/bpf/ |
| D | README.rst | 4 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-v4.19/Documentation/x86/ |
| D | intel_mpx.txt | 36 2) That setup code allocates (virtual) space for the "bounds directory",
37 points the "bndcfgu" register to the directory (must also set the valid
47 succeed, and notes the location of the bounds directory. Userspace is
48 expected to keep the bounds directory at that location. We note it
50 to access the bounds directory register is an expensive operation.
52 issues a bndstx instruction. Since the bounds directory is empty at
55 in the bounds directory point to the new table.
62 the table and remove the entry in the directory.
71 * allocates virtual space for the bounds directory (malloc() essentially)
72 * points the hardware BNDCFGU register at the directory
[all …]
|
| /Linux-v4.19/drivers/infiniband/hw/hfi1/ |
| D | eprom.c | 294 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-v4.19/Documentation/dev-tools/ |
| D | gcov.rst | 6 is exported in gcov-compatible format via the "gcov" debugfs directory.
8 directory and use gcov with the ``-o`` option as follows (requires root)::
14 in the current directory. In addition, graphical gcov front-ends such
65 - For all files in one directory::
88 Parent directory for all gcov-related files.
148 directory needs to be used instead (due to make's CURDIR handling).
155 from the gcov directory in sysfs:
160 must then be called with the -o option pointing to that directory.
162 Example directory setup on the build machine::
165 /tmp/out: kernel build directory as specified by make O=
[all …]
|
