directory (full) in projects: Linux-v6.6

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched full:directory (Results 1 – 25 of 3725) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...149

/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 the 27 need to lock two inodes of different type (dir vs non-dir), we lock directory 36 * check that source is not a directory 42 6) cross-directory rename. The trickiest in the whole bunch. Locking 55 the directory first. If we need to lock two inodes of the same type, 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 …]
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 had its attributes [all …]
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 …]
D	squashfs.rst	34 Max entries per directory unlimited unlimited 37 Directory indexes yes no 51 directory data are highly compacted, and packed on byte boundaries. Each 53 file type, i.e. regular file, directory, symbolic link, and block/char device 84 \| directory \| 101 the source directory, and checked for duplicates. Once all file data has been 102 written the completed inode, directory, fragment, export, uid/gid lookup and 127 (regular file, directory, device, etc.), the inode contents and length 131 directory inode are defined: inodes optimised for frequently occurring 139 in a directory table. Directories are accessed using the start address of [all …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.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 …]
/Linux-v6.6/tools/perf/pmu-events/arch/s390/cf_z10/
D	extended.json	7 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the retur… 14 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the installed ca… 21 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the insta… 28 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the installed ca… 35 …"PublicDescription": "A directory write to the Level-1 Instruction Cache directory where the insta… 42 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the installed ca… 49 …"PublicDescription": "A directory write to the Level-1 Data Cache directory where the installed ca… 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…
/Linux-v6.6/fs/freevxfs/
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 sizes. [all …]
/Linux-v6.6/fs/squashfs/
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 header [all …]
/Linux-v6.6/drivers/xen/
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 consumes itself in guest_calc_num_grefs() [all …]
/Linux-v6.6/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.
/Linux-v6.6/fs/jfs/
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 page) in jfs_create() 183 * FUNCTION: create a child directory in the parent directory <dip> [all …]
/Linux-v6.6/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`
/Linux-v6.6/fs/ntfs/
D	namei.c	3 * namei.c - NTFS kernel directory inode operations. Part of the Linux-NTFS 21 * ntfs_lookup - find the inode represented by a dentry in a directory inode 22 * @dir_ino: directory inode in which to look for the inode 27 * in the directory inode @dir_ino and if found attaches the inode to the 32 * converts the name to Unicode and walks the contents of the directory inode 34 * directory, the corresponding inode is loaded by calling ntfs_iget() on its 38 * If the name is not found in the directory, a NULL inode is inserted into the 45 * dcache and the dcache requiring only one dentry per directory, we deal with 48 * speed when the file/directory is looked up with the same case as returned by 51 * instead, where we search the directory for a fully matching file name [all …]

12 3 4 5 6 7 8 9 10 >>...149