| /linux/Documentation/filesystems/ext4/ |
| H A 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 …]
|
| H 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_ino …
40 for other filesystem features which are not referenced from standard directory
51 - Inode number of lost+found directory.
|
| H 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/ |
| H 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
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 …]
|
| H 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
36 file descriptor associated with the directory in which the event occurred.
[all …]
|
| H 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.
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 …]
|
| /linux/Documentation/ABI/testing/ |
| H 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
|
| H A 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.
|
| H 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
|
| H A 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
|
| H 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.
|
| H A 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
|
| H A D | sysfs-firmware-sgi_uv | 5 The /sys/firmware/sgi_uv directory contains information
8 Under that directory are a number of read-only attributes::
50 The /sys/firmware/sgi_uv directory also contains two directories::
55 The hubs directory contains a number of hub objects, each representing
59 Each hub object directory contains a number of read-only attributes::
94 Each hub object directory also contains a number of port objects,
99 Each port object directory contains a number of read-only attributes::
124 The pcibuses directory contains a number of PCI bus objects.
|
| /linux/tools/power/cpupower/ |
| H A 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
70 custom directory
75 'O' - build directory
76 'DESTDIR' - installation directory. This variable could also be setup in
100 build directory is the current one, build everything there and install
124 regardles of the root output directory.
132 installation directory
134 default directory
[all …]
|
| /linux/tools/perf/Documentation/ |
| H 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/scripts/clang-tools/ |
| H A 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/samples/bpf/ |
| H A 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/Documentation/driver-api/driver-model/ |
| H 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/Documentation/networking/ |
| H 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/drivers/infiniband/hw/hfi1/ |
| H 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/i2c/ |
| H A D | i2c-sysfs.rst | 37 Typically, the Linux Sysfs filesystem is mounted at the ``/sys`` directory,
40 There is a list of symbolic links under that directory. The links that
65 controllers. Linux kernel has I2C bus drivers under source directory
126 | |-- 73-0040 (I2C sensor device with hwmon directory)
139 is to read the symbolic link ``device`` under the I2C bus directory by using
143 in logical I2C bus directory which is fanned out from another I2C bus.
147 If the symbolic link points to a directory ending with ``.i2c``, it should be a
154 ls: /sys/bus/i2c/devices/i2c-7/mux_device: No such file or directory
157 link ``mux_device`` under its directory. And if the kernel software developer
162 presented by the current directory has to be a logical bus. The I2C bus pointed
[all …]
|
| /linux/Documentation/dev-tools/ |
| H A 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
61 - For all files in one directory::
95 Parent directory for all gcov-related files.
157 directory needs to be used instead (due to make's CURDIR handling).
166 from the gcov directory in sysfs:
171 must then be called with the -o option pointing to that directory.
173 Example directory setup on the build machine::
176 /tmp/out: kernel build directory as specified by make O=
[all …]
|
| /linux/Documentation/arch/sh/ |
| H A D | new-machine.rst | 17 The first thing to note is the new directory structure. Under 2.4, most
21 companion chip type, and CPU type. Looking at a tree view of this directory
96 In the first case, this is just a matter of making a directory for your
99 it makes more sense to have a common top-level arch/sh/boards/ directory
103 After you have setup your new arch/sh/boards/ directory, remember that you
104 should also add a directory in include/asm-sh for headers localized to this
106 seamlessly with the build system, it's best to have this directory the same
107 as the arch/sh/boards/ directory name, though if your board is again part of
109 overloading), and you can feel free to name the directory after the family
218 the board directory as it appears in arch/sh/boards, even if it is in a
[all …]
|
| /linux/drivers/mtd/parsers/ |
| H A D | redboot.c | 36 static int directory = CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK; variable
37 module_param(directory, int, 0);
67 * directory block pointer. in parse_redboot_of()
69 directory = dirblock; in parse_redboot_of()
94 if (directory < 0) { in parse_redboot_partitions()
95 offset = master->size + directory * master->erasesize; in parse_redboot_partitions()
105 offset = (unsigned long) directory * master->erasesize; in parse_redboot_partitions()
133 if (!memcmp(buf[i].name, "FIS directory", 14)) { in parse_redboot_partitions()
134 /* This is apparently the FIS directory entry for the in parse_redboot_partitions()
135 * FIS directory itsel in parse_redboot_partitions()
[all...] |
| /linux/drivers/xen/ |
| H A D | xen-front-pgdir-shbuf.c | 4 * Xen frontend/backend page directory based shared buffer
45 * e.g. if grefs are required for page directory only or the buffer
50 /* Fill page directory according to para-virtual display protocol. */
66 * page directory. Usually this is passed to the backend,
70 * \param buf shared buffer which page directory is of interest.
72 * page directory.
141 kfree(buf->directory); in xen_front_pgdir_shbuf_free()
154 * Get the number of pages the page directory consumes itself.
171 /* Only for pages the page directory consumes itself. */ in backend_calc_num_grefs()
184 * Number of pages the page directory consume in guest_calc_num_grefs()
[all...] |