directory (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

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

/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… 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 cac… 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 cac… 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 where the returned cac… 118 "BriefDescription": "Directory Write Level 1 Data Cache from L2-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 L2-Cache", [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… 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 cac… 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 cac… 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 where the returned cac… 118 "BriefDescription": "Directory Write Level 1 Data Cache from L2-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 L2-Cache", [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… 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/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… 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/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 26 directory is of course signified by reaching the end of the file. Unused [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… 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/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 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/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 and non-directory is [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 and the combined result [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 had its attributes [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/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 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/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	dirtree.c	34 * Directory Tree Structure Validation 37 * Validating the tree qualities of the directory tree structure can be 41 * disconnected cycles. If the tree is not frozen, directory updates can move 44 * Directory parent pointers change that by enabling an incremental approach to 61 * directory tree structure. Second, because we're walking upwards in a tree 63 * directory update hook to invalidate the scan results if one of the paths 93 /* Set us up to look for directory loops. / 168 If this path is more than 2 billion steps long, this directory tree in xchk_dirpath_append() 191 * Create an xchk_path for each parent pointer of the directory that we're 198 * are too many parent pointers for this directory [all...]
/linux/fs/isofs/
H A D	isofs.h	`156 /* Every directory can have many redundant directory entries scattered 157 * throughout the directory tree. First there is the directory entry 158 * with the name of the directory stored in the parent directory. 159 * Then, there is the "." directory entry stored in the directory 160 * itself. Finally, there are possibly many ".." directory entries 166 * the many redundant entries for each 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	239 * The @block is expected to be root directory. in tb_property_parse_dir() 259 * tb_property_create_dir() - Creates new property directory 260 * @uuid: UUID used to identify the particular directory in tb_property_create_dir() 262 * Creates new, empty property directory. If @uuid is %NULL then the in tb_property_create_dir() 263 * directory is assumed to be root directory. in tb_property_create_dir() 311 * tb_property_free_dir() - Release memory allocated for property directory in tb_property_free_dir() 312 * @dir: Directory to release in tb_property_free_dir() 314 * This will release all the memory the directory occupies including all in tb_property_free_dir() 354 /* Reserve dword padding after each directory */ in tb_property_dir_length() [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 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/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 consumes itself in guest_calc_num_grefs() [all …]
/linux/rust/kernel/
H A D	debugfs.rs	62 /// Owning handle to a DebugFS directory. in create() 64 /// The directory in the filesystem represented by [`Dir`] will be removed when handle has been in create() 76 /// Create a new directory in DebugFS. If `parent` is [`None`], it will be created at the root. in create_file() 87 // If Arc creation fails, the `Entry` will be dropped, so the directory will be in create_file() 124 /// Create a new directory in DebugFS at the root. in subdir() 136 /// Creates a subdirectory within this directory. 149 /// Creates a read-only file in this directory. in read_only_file() 177 /// Creates a read-only binary file in this directory. in read_binary_file() 202 /// Creates a read-only file in this directory, with contents from a callback. 246 /// Creates a read-write file in this directory in read_write_binary_file() [all...]
/linux/fs/jfs/
H A D	namei.c	52 * FUNCTION: create a regular file in the parent directory <dip> 55 * PARAMETER: dip - parent directory vnode 68 struct inode ip = NULL; / child directory inode / in jfs_create() 70 struct component_name dname; / child directory name / in jfs_create() 82 search parent directory for entry/freespace in jfs_create() 83 * (dtSearch() returns parent directory page pinned) in jfs_create() 91 * begin the transaction before we search the directory. in jfs_create() 134 * create entry in parent directory for child directory in jfs_create() 135 * (dtInsert() releases parent directory page) in jfs_create() 184 * FUNCTION: create a child directory in the parent directory <dip> [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/adfs/
H A D	dir_f.c	7 * E and F format directory handling 81 * word of the last directory entry. This in adfs_dir_checkbyte() 107 * The directory tail is in the final bh in adfs_dir_checkbyte() 140 /* Read and check that a directory is valid / 172 convert a disk-based directory entry to a Linux ADFS directory entry 198 * convert a Linux ADFS directory entry to a disk-based directory entry 211 * get a directory entry. Note that the caller is responsible 282 adfs_error(dir->sb, "error reading directory entry"); in adfs_f_update() 291 /* Update the directory entry with the new object state / in adfs_f_update() 294 / Write the directory entry back to the directory */ in adfs_f_update() [all …]
/linux/fs/sysfs/
H A D	dir.c	36 * sysfs_create_dir_ns - create a directory for an object with a namespace tag 37 * @kobj: object we're creating directory for 72 * sysfs_remove_dir - remove an object's directory. 76 * the directory before we remove the directory, and we've inlined 130 * sysfs_create_mount_point - create an always empty directory 131 * @parent_kobj: kobject that will contain this always empty directory 132 * @name: The name of the always empty directory to add 150 * sysfs_remove_mount_point - remove an always empty directory. 151 * @parent_kobj: kobject that will contain this always empty directory 152 * @name: The name of the always empty directory to remove
/linux/fs/xfs/libxfs/
H A D	xfs_dir2.c	41 * Convert inode mode to directory entry filetype 129 /* set up directory geometry / in xfs_da_mount() 198 Return 1 if directory contains only "." and "..". 235 * Initialize a directory with its "." and ".." entries. 321 * Enter a name in a directory, or check for available space. 420 * Lookup a name in a directory, give back the inode number. 489 * Remove an entry from a directory. 546 * Replace the inode number of a directory entry. 586 * See if this entry can be added to the directory without allocating space. 602 * Add a block to the directory [all...]

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