Searched full:file (Results 1 – 25 of 1723) sorted by relevance
12345678910>>...69
| /Documentation/driver-api/media/ |
| D | v4l2-fh.rst | 3 V4L2 File handlers
6 struct v4l2_fh provides a way to easily keep file handle specific
15 whether a driver uses :c:type:`v4l2_fh` as its ``file->private_data`` pointer
19 struct v4l2_fh is allocated as a part of the driver's own file handle
20 structure and ``file->private_data`` is set to it in the driver's ``open()``
29 Drivers can extract their own file handle structure by using the container_of
43 int my_open(struct file *file)
59 file->private_data = &my_fh->fh;
64 int my_release(struct file *file)
66 struct v4l2_fh *fh = file->private_data;
[all …]
|
| /Documentation/filesystems/ |
| D | files.rst | 4 File management in the Linux kernel
7 This document describes how locking for files (struct file)
8 and file descriptor table (struct files) works.
10 Up until 2.6.12, the file descriptor table has been protected
12 ->file_lock protected accesses to all the file related fields
13 of the table. ->count was used for sharing the file descriptor
17 a put_files_struct() frees the file descriptor (fd) table.
18 The files (struct file) themselves are protected using
21 In the new lock-free model of file descriptor management,
23 based on RCU. The file descriptor table contains multiple
[all …]
|
| D | zonefs.rst | 10 zonefs is a very simple file system exposing each zone of a zoned block device
11 as a file. Unlike a regular POSIX-compliant file system with native zoned block
15 of the file (append only writes).
18 than to a full-featured POSIX file system. The goal of zonefs is to simplify
20 raw block device file accesses with a richer file API, avoiding relying on
21 direct block device file ioctls which may be more obscure to developers. One
24 by allowing SSTables to be stored in a zone file similarly to a regular file
26 of the higher level construct "one file is one zone" can help reducing the
62 by sub-directories. This file structure is built entirely using zone information
72 and populates the mount point with a static file tree solely based on this
[all …]
|
| D | fsverity.rst | 6 fs-verity: read-only file-based authenticity protection
22 causes the filesystem to build a Merkle tree for the file and persist
23 it to a filesystem-specific location associated with the file.
25 After this, the file is made readonly, and all reads from the file are
26 automatically verified against the file's Merkle tree. Reads of any
30 the "fs-verity file digest", which is a hash that includes the Merkle
31 tree root hash) that fs-verity is enforcing for the file. This ioctl
32 executes in constant time, regardless of the file size.
34 fs-verity is essentially a way to hash a file in constant time,
44 However, because fs-verity makes retrieving the file hash extremely
[all …]
|
| D | romfs.rst | 4 ROMFS - ROM File System
11 file system which doesn't take up useful memory from the router
23 To create such a file system, you'll need a user program named
51 byte boundaries for fast access. The minimum space a file will take
52 is 32 bytes (this is an empty file, with a less than 16 character
53 name). The maximum overhead for any non-empty file is the header, and
55 bytes. This is quite rare however, since most file names are longer
74 xx | file |
90 The following bytes are now part of the file system; each file header
96 0 | next filehdr|X| The offset of the next file header
[all …]
|
| D | hpfs.rst | 14 Chris Smith, 1993, original read-only HPFS, some code and hpfs structures file
30 File name lowercasing in readdir.
34 text file than to damage binary file). If you want to change that list,
37 computer decide whether file is text or binary. For example, DJGPP
44 used for debugging (for example it checks if file is allocated in
60 File names
64 are case sensitive, so for example when you create a file FOO, you can use
68 bootsect.s. When searching for file thats name has characters >= 128, codepages
70 OS/2 ignores dots and spaces at the end of file name, so this driver does as
71 well. If you create 'a. ...', the file 'a' will be created, but you can still
[all …]
|
| /Documentation/power/ |
| D | swsusp-and-swap-files.rst | 11 (2) the header of a swap file is not in the first block of the partition that
16 In principle the location of a swap file's header may be determined with the
18 filesystem holding the swap file to be mounted, and if this filesystem is
20 identify a swap file swsusp uses the name of the partition that holds the file
21 and the offset from the beginning of the partition at which the swap file's
25 In order to use a swap file with swsusp, you need to:
27 1) Create the swap file and make it active, eg.::
33 2) Use an application that will bmap the swap file with the help of the
34 FIBMAP ioctl and determine the location of the file's swap header, as the
36 holds the swap file.
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-ufs | 5 This file contains the auto-hibernate idle timer setting of a
19 Description: This file shows the device type. This is one of the UFS
23 The file is read only.
29 Description: This file shows the device class. This is one of the UFS
33 The file is read only.
39 Description: This file shows the UFS storage subclass. This is one of
43 The file is read only.
49 Description: This file shows the protocol supported by an UFS device.
54 The file is read only.
60 Description: This file shows number of logical units. This is one of
[all …]
|
| D | sysfs-class-firmware | 5 Description: The data sysfs file is used for firmware-fallback and for
6 firmware uploads. Cat a firmware image to this sysfs file
7 after you echo 1 to the loading sysfs file. When the firmware
8 image write is complete, echo 0 to the loading sysfs file. This
17 Description: Write-only. For firmware uploads, write a "1" to this file to
30 for the status sysfs file and <ERROR> will be one of the
32 "invalid-file-size", "read-write-error", "flash-wearout". The
33 error sysfs file is only meaningful when the current firmware
34 upload status is "idle". If this file is read while a firmware
41 Description: The loading sysfs file is used for both firmware-fallback and
[all …]
|
| D | sysfs-power | 13 The /sys/power/state file controls system sleep states.
14 Reading from this file returns the available sleep state
18 Writing one of the above strings to this file causes the system
28 The /sys/power/mem_sleep file controls the operating mode of
33 file described above) is enclosed in square brackets.
35 Writing one of the above strings to this file causes the mode
46 The /sys/power/disk file controls the operating mode of the
47 suspend-to-disk mechanism. Reading from this file returns
79 file one of the accepted strings:
95 The /sys/power/image_size file controls the size of the image
[all …]
|
| D | sysfs-kernel-mm-damon | 17 Description: Writing a number 'N' to this file creates the number of
24 Description: Writing 'on' or 'off' to this file makes the kdamond starts or
25 stops, respectively. Reading the file returns the keywords
26 based on the current status. Writing 'commit' to this file
29 this file makes the kdamond reads the quota goal files again.
30 Writing 'update_schemes_stats' to the file updates contents of
32 'update_schemes_tried_regions' to the file updates contents of
34 kdamond. Writing 'update_schemes_tried_bytes' to the file
36 kdamond. Writing 'clear_schemes_tried_regions' to the file
38 'update_schemes_effective_quotas' to the file updates
[all …]
|
| D | sysfs-ptp | 21 This file contains the name of the PTP hardware clock
32 This file contains the PTP hardware clock's maximum
40 This file contains the maximum number of ptp vclocks.
47 This file contains the number of periodic or one shot
54 This file contains the number of external timestamp
61 This file contains the number of programmable periodic
68 This file contains the number of programmable pins
75 This file contains the number of virtual PTP clocks in
88 This directory contains one file for each programmable
89 pin offered by the PTP hardware clock. The file name
[all …]
|
| D | sysfs-block-zram | 5 The disksize file is read-write and specifies the disk size
14 The initstate file is read-only and shows the initialization
21 The reset file is write-only and allows resetting the
29 The max_comp_streams file is read-write and specifies the
37 The comp_algorithm file is read-write and lets to show
45 The mem_used_max file is write-only and is used to reset
55 The mem_limit file is write-only and specifies the maximum
64 The compact file is write-only and trigger compaction for
72 The io_stat file is read-only and accumulates device's I/O
74 failed_reads, failed_writes, etc. File format is similar to
[all …]
|
| D | sysfs-bus-event_source-devices-hv_gpci | 81 This sysfs file exposes the cpumask which is designated to make
88 This sysfs file exposes the system topology information by making HCALL
92 * This sysfs file will be created only for power10 and above platforms.
94 * User needs root privileges to read data from this sysfs file.
96 * This sysfs file will be created, only when the HCALL returns "H_SUCCESS",
102 * The end user reading this sysfs file must decode the content as per
105 Possible error codes while reading this sysfs file:
120 This sysfs file exposes the system topology information by making HCALL
124 * This sysfs file will be created only for power10 and above platforms.
126 * User needs root privileges to read data from this sysfs file.
[all …]
|
| D | sysfs-class-wakeup | 12 This file contains the name of the wakeup source.
18 This file contains the number of times the wakeup source was
25 This file contains the number of signaled wakeup events
32 This file contains the number of times the wakeup source might
39 This file contains the number of times the wakeup source's
46 This file contains the amount of time the wakeup source has
48 source is not active, this file contains '0'.
54 This file contains the total amount of time this wakeup source
61 This file contains the maximum amount of time this wakeup
68 This file contains the monotonic clock time when the wakeup
[all …]
|
| D | sysfs-ocfs2 | 12 The /sys/fs/ocfs2/max_locking_protocol file displays version
23 Reading from this file returns a single line, the major
26 This file is read-only. The value is compiled into the
33 The /sys/fs/ocfs2/loaded_cluster_plugins file describes
43 Reading from this file returns the names of all loaded
46 This file is read-only. Its contents may change as
56 file as well. Only one plugin can be used at a time.
58 Reading from this file returns the name of the active plugin
61 This file is read-only. Which plugin is active depends on
70 The /sys/fs/ocfs2/cluster_stack file contains the name
[all …]
|
| /Documentation/filesystems/spufs/ |
| D | spufs.rst | 10 spufs - the SPU file system
16 The SPU file system is used on PowerPC machines that implement the Cell
20 The file system provides a name space similar to posix shared memory or
21 message queues. Users that have write permissions on the file system
45 the operations supported on regular file systems. This list details the
57 possible operations, e.g. read access on the wbox file.
64 accessed like a regular shared memory file and contains both code and
66 open mem file are:
71 file. The file size is the size of the local storage of the SPU,
81 The first SPU to CPU communication mailbox. This file is read-only and
[all …]
|
| /Documentation/admin-guide/ |
| D | filesystem-monitoring.rst | 4 File system Monitoring with fanotify
7 File system Error Reporting
10 Fanotify supports the FAN_FS_ERROR event type for file system-wide error
11 reporting. It is meant to be used by file system health monitoring
13 sysadmin, start recovery) when a file system problem is detected.
16 for a monitoring tool to know a problem in the file system has happened.
20 early file system problem detection and reporting recovery tools.
22 When a file system operation fails, it is common for dozens of kernel
26 error that occurred for a file system since the last notification, and
33 At the time of this writing, the only file system that emits FAN_FS_ERROR
[all …]
|
| /Documentation/virt/kvm/devices/ |
| D | vfio.rst | 16 KVM, a reference to the VFIO file is held by KVM.
24 KVM_DEV_VFIO_FILE_ADD: Add a VFIO file (group/device) to VFIO-KVM device
27 kvm_device_attr.addr points to an int32_t file descriptor for the
28 VFIO file.
30 KVM_DEV_VFIO_FILE_DEL: Remove a VFIO file (group/device) from VFIO-KVM
33 kvm_device_attr.addr points to an int32_t file descriptor for the
34 VFIO file.
52 - @groupfd is a file descriptor for a VFIO group;
53 - @tablefd is a file descriptor for a TCE table allocated via
56 The FILE/GROUP_ADD operation above should be invoked prior to accessing the
[all …]
|
| /Documentation/PCI/ |
| D | sysfs-pci.rst | 37 file function
58 ro - read only file
59 rw - file is readable and writable
60 wo - write only file
61 mmap - file is mmapable
62 ascii - file contains ascii text
63 binary - file contains binary data
64 cpumask - file contains a cpumask type
69 the exception of the 'rom' file. Writable files can be used to perform
71 mmapable files are available via an mmap of the file at offset 0 and can be
[all …]
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-driver-hid-roccat-ryos | 4 Description: When written, this file lets one select which data from which
6 This file is writeonly.
24 Description: When written, this file lets one set the default of all keys for
27 Before reading this file, control has to be written to select
34 Description: When written, this file lets one set the function of the
37 Before reading this file, control has to be written to select
44 Description: When written, this file lets one set the function of the macro
47 Before reading this file, control has to be written to select
54 Description: When written, this file lets one set the function of the
57 Before reading this file, control has to be written to select
[all …]
|
| D | sysfs-driver-hid-roccat-isku | 8 When written, this file sets the number of the startup profile
15 Description: When read, this file returns general data like firmware version.
17 This file is readonly.
23 Description: When written, this file lets one deactivate certain keys like
27 Before reading this file, control has to be written to select
34 Description: When written, this file lets one set the function of the
37 Before reading this file, control has to be written to select
44 Description: When written, this file lets one set the function of the
47 Before reading this file, control has to be written to select
54 Description: When written, this file lets one set the function of the
[all …]
|
| /Documentation/filesystems/ext4/ |
| D | allocators.rst | 14 up file rewrites significantly. Therefore, it is useful to reduce
18 allocator. When a file is first created, the block allocator
19 speculatively allocates 8KiB of disk space to the file on the assumption
20 that the space will get written soon. When the file is closed, the
23 files) then the file data gets written out in a single multi-block
25 Under this scheme, when a file needs more blocks to absorb file writes,
33 file's data blocks in the same block group as its inode. This cuts down
34 on the seek penalty when the filesystem first has to read a file's inode
35 to learn where the file's data blocks live and then seek over to the
36 file's data blocks to begin I/O operations.
[all …]
|
| /Documentation/trace/coresight/ |
| D | coresight-etm4x-reference.rst | 22 :File: ``mode`` (rw)
39 :File: ``reset`` (wo)
49 :File: ``enable_source`` (wo)
62 :File: ``cpu`` (ro)
74 :File: ``ts_source`` (ro)
88 :File: ``addr_idx`` (rw)
101 :File: ``addr_range`` (rw)
124 :File: ``addr_single`` (rw)
137 :File: ``addr_start`` (rw)
149 :File: ``addr_stop`` (rw)
[all …]
|
| /Documentation/driver-api/early-userspace/ |
| D | buffer-format.rst | 20 initramfs buffer is thus a single .cpio.gz file.
59 c_ino 8 bytes File inode number
60 c_mode 8 bytes File mode and permissions
61 c_uid 8 bytes File uid
62 c_gid 8 bytes File gid
66 c_maj 8 bytes Major part of file device number
67 c_min 8 bytes Minor part of file device number
76 on Linux, and encodes the file type and file permissions.
78 The c_filesize should be zero for any file which is not a regular file
97 link rather than a second copy of the file is created. It is not
[all …]
|
12345678910>>...69