| /linux/tools/perf/pmu-events/arch/s390/cf_z16/ |
| H A D | extended.json | 7 "PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in a Read-Only state in the cache but has been updated to be in the Exclusive state that allows stores to the cache line."
97 "BriefDescription": "Directory Write Level 1 Data Cache from L2-Cache",
98 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from the requestors Level-2 cache."
104 "BriefDescription": "Directory Write Level 1 Data Cache from L2-Cache with Intervention",
105 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from the requestors Level-2 cache with intervention."
111 "BriefDescription": "Directory Write Level 1 Data Cache from L2-Cache with Chip HP Hit",
112 "PublicDescription": "A directory write to the Level-1 Data cache directory wher
[all...] |
| /linux/tools/perf/pmu-events/arch/s390/cf_z13/ |
| H A D | extended.json | 7 "PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in a Read-Only state in the cache but has been updated to be in the Exclusive state that allows stores to the cache line."
42 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from the Level-2 Data cache."
63 "PublicDescription": "A directory write to the Level-1 Instruction cache directory where the returned cache line was sourced from the Level-2 Instruction cache."
112 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from an On-Chip Level-3 cache without intervention."
119 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from an On-Chip Level-3 cache with intervention."
126 "PublicDescription": "A directory writ
[all...] |
| /linux/tools/perf/pmu-events/arch/s390/cf_z17/ |
| H A D | extended.json | 7 "PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in a Read-Only state in the cache but has been updated to be in the Exclusive state that allows stores to the cache line."
97 "BriefDescription": "Directory Write Level 1 Data Cache from L2-Cache",
98 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from the requestors Level-2 cache."
104 "BriefDescription": "Directory Write Level 1 Data Cache from L2-Cache with Intervention",
105 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from the requestors Level-2 cache with intervention."
111 "BriefDescription": "Directory Write Level 1 Data Cache from L2-Cache with Chip HP Hit",
112 "PublicDescription": "A directory write to the Level-1 Data cache directory wher
[all...] |
| /linux/Documentation/filesystems/ext4/ |
| H A 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
[all...] |
| /linux/tools/perf/pmu-events/arch/s390/cf_z14/ |
| H A D | extended.json | 7 "PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in a Read-Only state in the cache but has been updated to be in the Exclusive state that allows stores to the cache line."
42 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from the Level-2 Data cache."
63 "PublicDescription": "A directory write to the Level-1 Instruction cache directory where the returned cache line was sourced from the Level-2 Instruction cache."
112 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from an On-Chip Level-3 cache without intervention."
119 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from On-Chip memory."
126 "PublicDescription": "A directory writ
[all...] |
| /linux/tools/perf/pmu-events/arch/s390/cf_z15/ |
| H A D | extended.json | 7 "PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in a Read-Only state in the cache but has been updated to be in the Exclusive state that allows stores to the cache line."
42 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from the Level-2 Data cache."
63 "PublicDescription": "A directory write to the Level-1 Instruction cache directory where the returned cache line was sourced from the Level-2 Instruction cache."
112 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from an On-Chip Level-3 cache without intervention."
119 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from On-Chip memory."
126 "PublicDescription": "A directory writ
[all...] |
| /linux/tools/perf/pmu-events/arch/s390/cf_zec12/ |
| H A D | extended.json | 21 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from the Level-2 Instruction cache."
28 "PublicDescription": "A directory write to the Level-1 Instruction cache directory where the returned cache line was sourced from the Level-2 Instruction cache."
35 "PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cache line was sourced from the Level-2 Data cache."
49 "PublicDescription": "A directory write to the Level-1 Data cache where the installed cache line was sourced from memory that is attached to the same book as the Data cache (Local Memory)."
56 "PublicDescription": "A directory write to the Level-1 Instruction cache where the installed cache line was sourced from memory that is attached to the same book as the Instruction cache (Local Memory)."
63 "PublicDescription": "A directory write to the Level-1 Data Cache where the line was originally in a Read-Only state in the cache but has been updated to be in the Exclusive state that allows stores to the cache line."
105 "PublicDescription": "A directory writ
[all...] |
| /linux/Documentation/filesystems/ |
| H A 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
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 an
[all...] |
| H A D | overlayfs.rst | 26 non-directory objects may report an st_dev from the lower filesystem or
29 over the lifetime of a non-directory object. Many applications and
92 It would be more correct to refer to an upper and lower 'directory
94 directory trees to be in the same filesystem and there is no
113 upper and lower filesystems and refers to a non-directory in either,
117 Where both upper and lower objects are directories, a merged directory
121 "upperdir" are combined into a merged directory::
126 The "workdir" needs to be an empty directory on the same filesystem
129 Then whenever a lookup is requested in such a merged directory, the
130 lookup is performed in each actual directory an
[all...] |
| H A D | dnotify.rst | 4 Linux Directory Notification
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 ha
[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 nam
[all...] |
| /linux/tools/perf/pmu-events/arch/s390/cf_z196/ |
| H A D | extended.json | 7 "PublicDescription": "A directory write to the Level-1 Data Cache directory where the returned cache line was sourced from the Level-2 cache."
14 "PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the returned cache line was sourced from the Level-2 cache."
42 "PublicDescription": "A directory write to the Level-1 Data Cache directory where the returned cache line was sourced from an Off Book Level-3 cache."
49 "PublicDescription": "A directory write to the Level-1 Data Cache directory where the returned cache line was sourced from an On Book Level-4 cache."
56 "PublicDescription": "A directory write to the Level-1 Instruction Cache directory wher
[all...] |
| /linux/Documentation/admin-guide/mm/damon/ |
| H A D | usage.rst | 36 creates multiple directories and files under its sysfs directory,
38 from the files under the directory.
55 directory is having ``/`` suffix, and files in each directory are separated by
104 has one directory named ``admin``. The directory contains the files for
106 having the root permission could use this directory.
113 Under the ``admin`` directory, one directory, ``kdamonds``, which has files for
116 details) exists. In the beginning, this directory ha
[all...] |
| /linux/fs/xfs/scrub/ |
| H A D | dir_repair.c | 50 * Directory Repair
53 * We repair directories by reading the directory data blocks looking for
54 * directory entries that look salvageable (name passes verifiers, entry points
57 * directory to constrain memory use. Batching the construction of the
58 * temporary directory in this fashion reduces lock cycling of the directory
59 * being repaired and the temporary directory, and will later become important
63 * the directory by visiting each parent pointer of each file in the filesystem
65 * case, it is advantageous to stash all directory entries created from parent
67 * directory
[all...] |
| H A D | findparent.c | 40 * Finding the Parent of a Directory
43 * Directories have parent pointers, in the sense that each directory contains
45 * way to find the parent of a given directory is to scan every directory in
46 * the filesystem looking for a child dirent that references this directory.
48 * This module wraps the process of scanning the directory tree. It requires
49 * that @sc->ip is the directory whose parent we want to find, and that the
50 * caller hold only the IOLOCK on that directory. The scan itself needs to
51 * take the ILOCK of each directory visited.
58 * filesystem, such as noticing directory tre
[all...] |
| /linux/Documentation/PCI/endpoint/ |
| H 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::
22 Directory Structure
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>.
54 Every <EPF device> directory consists of the following entries that can be
80 interface should be added in 'primary' directory and symlink of endpoint
82 directory
[all...] |
| /linux/scripts/clang-tools/ |
| H A D | gen_compile_commands.py | 24 # The tools/ directory adopts a different build system, and produces .cmd
33 directory: The work directory where the objects were built.
41 directory_help = ('specify the output directory used for the kernel build '
42 '(defaults to the working directory)')
43 parser.add_argument('-d', '--directory', type=str, default='.',
61 'If nothing is specified, the current directory is searched')
67 os.path.realpath(args.directory),
70 args.paths if len(args.paths) > 0 else [args.directory])
73 def cmdfiles_in_dir(directory) argument
[all...] |
| /linux/drivers/thunderbolt/ |
| H A D | property.c | 214 * Upon success returns the parsed directory. In case of error returns
218 * The @block is expected to be root directory.
236 * tb_property_create_dir() - Creates new property directory
237 * @uuid: UUID used to identify the particular directory
239 * Creates new, empty property directory. If @uuid is %NULL then the
240 * directory is assumed to be root directory.
286 * tb_property_free_dir() - Release memory allocated for property directory
287 * @dir: Directory to release
289 * This will release all the memory the directory occupie
[all...] |
| /linux/tools/perf/pmu-events/arch/s390/cf_z10/ |
| H A D | extended.json | 7 "PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the returned cache line was sourced from the Level-2 (L1.5) cache."
14 "PublicDescription": "A directory write to the Level-1 Data Cache directory where the installed cache line was sourced from the Level-2 (L1.5) cache."
21 "PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the installed cache line was sourced from the Level-3 cache that is on the same book as the Instruction cache (Local L2 cache)."
28 "PublicDescription": "A directory write to the Level-1 Data Cache directory where the installed cache line was source from the Level-3 cache that is on the same book as the Data cache (Local L2 cache)."
35 "PublicDescription": "A directory write to the Level-1 Instruction Cache directory wher
[all...] |
| /linux/fs/freevxfs/ |
| H A D | vxfs_dir.h | 9 * Veritas filesystem driver - directory structure.
11 * This file contains the definition of the vxfs directory format.
16 * VxFS directory block header.
18 * This entry is the head of every filesystem block in a directory.
20 * a hash for speeding up directory search (lookup).
33 * of an VxFS directory entry.
38 * VxFS directory entry.
49 * VXFS_DIRPAD defines the directory entry boundaries, is _must_ be
51 * VXFS_NAMEMIN is the length of a directory entry with a NULL d_name.
53 * usable for directory size
[all...] |
| /linux/fs/squashfs/ |
| H A D | namei.c | 15 * in a directory table. Directories are accessed using the start address of
16 * the metablock containing the directory and the offset into the
23 * Directories are therefore organised in a two level list, a directory
24 * header containing the shared start block value, and a sequence of directory
25 * entries, each of which share the shared start block. A new directory header
26 * is written once/if the inode start block changes. The directory
27 * header/directory entry list is repeated as many times as necessary.
29 * Directories are sorted, and can contain a directory index to speed up
30 * file lookup. Directory indexes store one entry per metablock, each entry
31 * storing the index/filename mapping to the first directory heade
[all...] |
| /linux/Documentation/driver-api/driver-model/ |
| H 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
[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...] |
| /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
|
| /linux/fs/jfs/ |
| H A D | namei.c | 51 * FUNCTION: create a regular file in the parent directory <dip>
54 * PARAMETER: dip - parent directory vnode
67 struct inode *ip = NULL; /* child directory inode */ in jfs_create()
69 struct component_name dname; /* child directory name */ in jfs_create()
81 * search parent directory for entry/freespace in jfs_create()
82 * (dtSearch() returns parent directory page pinned) in jfs_create()
90 * begin the transaction before we search the directory. in jfs_create()
133 * create entry in parent directory for child directory in jfs_create()
134 * (dtInsert() releases parent directory pag in jfs_create()
[all...] |