| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/s390/cf_z16/ |
| D | extended.json | 7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 97 "BriefDescription": "Directory Write Level 1 Data Cache from Cache", 98 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 104 "BriefDescription": "Directory Write Level 1 Data Cache from Cache with Intervention", 105 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 111 "BriefDescription": "Directory Write Level 1 Data Cache from Cache with Chip HP Hit", 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 118 "BriefDescription": "Directory Write Level 1 Data Cache from Cache with Drawer HP Hit", 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 125 "BriefDescription": "Directory Write Level 1 Data Cache from On-Chip Cache", [all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/s390/cf_z13/ |
| D | extended.json | 7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/s390/cf_z13/ |
| D | extended.json | 7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/s390/cf_z14/ |
| D | extended.json | 7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/s390/cf_z14/ |
| D | extended.json | 7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
|
| /kernel/linux/linux-5.10/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 non-directory; target - if it's a non-directory or about to be removed. 32 and the target because mixing directory and non-directory is allowed 39 * check that source is not a directory 45 6) cross-directory rename. The trickiest in the whole bunch. Locking 66 If no directory is its own ancestor, the scheme above is deadlock-free. [all …]
|
| 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 94 It would be more correct to refer to an upper and lower 'directory 96 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 and the combined result [all …]
|
| /kernel/linux/linux-6.6/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 non-directory; target - if it's a non-directory or about to be removed. 32 and the target because mixing directory and non-directory is allowed 39 * check that source is not a directory 45 6) cross-directory rename. The trickiest in the whole bunch. Locking 66 If no directory is its own ancestor, the scheme above is deadlock-free. [all …]
|
| 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 and the combined result [all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/s390/cf_z15/ |
| D | extended.json | 7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/s390/cf_z15/ |
| D | extended.json | 7 …"PublicDescription": "A directory write to the Level-1 Data cache where the line was originally in… 42 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 63 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 133 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 140 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 147 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 154 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/s390/cf_zec12/ |
| D | extended.json | 21 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 28 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 35 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 49 …"PublicDescription": "A directory write to the Level-1 Data cache where the installed cache line w… 56 …"PublicDescription": "A directory write to the Level-1 Instruction cache where the installed cache… 63 …"PublicDescription": "A directory write to the Level-1 D-Cache where the line was originally in a … 105 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/s390/cf_zec12/ |
| D | extended.json | 21 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 28 …"PublicDescription": "A directory write to the Level-1 Instruction cache directory where the retur… 35 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 49 …"PublicDescription": "A directory write to the Level-1 Data cache where the installed cache line w… 56 …"PublicDescription": "A directory write to the Level-1 Instruction cache where the installed cache… 63 …"PublicDescription": "A directory write to the Level-1 Data Cache where the line was originally in… 105 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 112 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 119 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… 126 …"PublicDescription": "A directory write to the Level-1 Data cache directory where the returned cac… [all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/s390/cf_z196/ |
| D | extended.json | 7 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the returned cache … 14 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the returned cache … 42 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the returned cache … 49 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the returned cache … 56 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the returned cache … 63 …"PublicDescription": "A directory write to the Level-1 D-Cache where the line was originally in a … 70 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the returned cache … 77 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the returned cache … 91 …"PublicDescription": "A directory write to the Level-1 D-Cache where the installed cache line was … 98 …"PublicDescription": "A directory write to the Level-1 I-Cache where the installed cache line was … [all …]
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/s390/cf_z196/ |
| D | extended.json | 7 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the returned cac… 14 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the retur… 42 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the returned cac… 49 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the returned cac… 56 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the retur… 63 …"PublicDescription": "A directory write to the Level-1 Data Cache where the line was originally in… 70 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the returned cac… 77 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the retur… 91 …"PublicDescription": "A directory write to the Level-1 Data Cache where the installed cache line w… 98 …"PublicDescription": "A directory write to the Level-1 Instruction Cache where the installed cache… [all …]
|
| /kernel/linux/linux-6.6/fs/isofs/ |
| D | isofs.h | 154 /* Every directory can have many redundant directory entries scattered 155 * throughout the directory tree. First there is the directory entry 156 * with the name of the directory stored in the parent directory. 157 * Then, there is the "." directory entry stored in the directory 158 * itself. Finally, there are possibly many ".." directory entries 164 * the many redundant entries for each directory. We normalize the 165 * block and offset by always making them point to the "." directory. 167 * Notice that we do not use the entry for the directory with the name 168 * that is located in the parent directory. Even though choosing this 169 * first directory is more natural, it is much easier to find the "." [all …]
|
| /kernel/linux/linux-5.10/fs/isofs/ |
| D | isofs.h | 154 /* Every directory can have many redundant directory entries scattered 155 * throughout the directory tree. First there is the directory entry 156 * with the name of the directory stored in the parent directory. 157 * Then, there is the "." directory entry stored in the directory 158 * itself. Finally, there are possibly many ".." directory entries 164 * the many redundant entries for each directory. We normalize the 165 * block and offset by always making them point to the "." directory. 167 * Notice that we do not use the entry for the directory with the name 168 * that is located in the parent directory. Even though choosing this 169 * first directory is more natural, it is much easier to find the "." [all …]
|
| /kernel/linux/linux-6.6/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 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 …]
|
| /kernel/linux/linux-6.6/scripts/clang-tools/ |
| 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.abspath(args.directory), 70 args.paths if len(args.paths) > 0 else [args.directory]) 73 def cmdfiles_in_dir(directory): argument 74 """Generate the iterator of .cmd files found under the directory. [all …]
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/mm/damon/ |
| D | usage.rst | 42 creates multiple directories and files under its sysfs directory, 44 from the files under the directory. 61 directory is having ``/`` suffix, and files in each directory are separated by 101 has one directory named ``admin``. The directory contains the files for 103 having the root permission could use this directory. 112 Under the ``admin`` directory, one directory, ``kdamonds``, which has files for 113 controlling the kdamonds exist. In the beginning, this directory has only one 115 of child directories named ``0`` to ``N-1``. Each directory represents each 121 In each kdamond directory, two files (``state`` and ``pid``) and one directory 133 DAMON-based operation scheme action tried regions directory for each [all …]
|
| /kernel/linux/linux-5.10/scripts/clang-tools/ |
| D | gen_compile_commands.py | 31 directory: The work directory where the objects were built. 39 directory_help = ('specify the output directory used for the kernel build ' 40 '(defaults to the working directory)') 41 parser.add_argument('-d', '--directory', type=str, default='.', 59 'If nothing is specified, the current directory is searched') 65 os.path.abspath(args.directory), 68 args.paths if len(args.paths) > 0 else [args.directory]) 71 def cmdfiles_in_dir(directory): argument 72 """Generate the iterator of .cmd files found under the directory. 74 Walk under the given directory, and yield every .cmd file found. [all …]
|
| /kernel/linux/linux-6.6/drivers/thunderbolt/ |
| 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 occupies including all 329 /* Reserve dword padding after each directory */ in tb_property_dir_length() [all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/s390/cf_z10/ |
| D | extended.json | 7 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the returned cache … 14 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the installed cache… 21 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the installed cache… 28 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the installtion cac… 35 …"PublicDescription": "A directory write to the Level-1 I-Cache directory where the installed cache… 42 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the installed cache… 49 …"PublicDescription": "A directory write to the Level-1 D-Cache directory where the installed cache… 56 …"PublicDescription": "A directory write to the Level-1 I-Cache where the installed cache line was … 63 …"PublicDescription": "A directory write to the Level-1 D-Cache where the line was originally in a …
|