| /linux-6.1.9/Documentation/ABI/testing/ |
| D | sysfs-block-bcache | 5 A write to this file causes the backing device or cache to be
6 unregistered. If a backing device had dirty data in the cache,
9 all associated backing devices before unregistering themselves.
21 For a backing device that has cache, a symlink to
28 For backing devices: integer number of full cache hits,
35 For backing devices: integer number of cache misses.
41 For backing devices: cache hits as a percentage.
47 For backing devices: Threshold past which sequential IO will
63 For backing devices: When on, writeback caching is enabled and
72 For backing devices: when off, dirty data will not be written
[all …]
|
| D | configfs-usb-gadget-mass-storage | 23 file The path to the backing file for the LUN.
36 the function is active. It causes the backing
|
| D | sysfs-block-loop | 15 (RO) The path of the backing file that the loop device maps its
49 (RO) Shows if direct IO is being used to access backing file or
|
| D | sysfs-class-bdi | 23 The default backing dev, used for non-block device backed
63 If set, the backing device requires that all pages comprising a write
|
| D | sysfs-block-zram | 98 The backing_dev file is read-write and set up backing
115 huge page writeback to backing device.
121 The bd_stat file is read-only and represents backing device's
|
| /linux-6.1.9/arch/x86/kernel/cpu/sgx/ |
| D | main.c | 160 struct sgx_backing *backing) in __sgx_encl_ewb() argument
168 pginfo.contents = (unsigned long)kmap_atomic(backing->contents); in __sgx_encl_ewb()
169 pginfo.metadata = (unsigned long)kmap_atomic(backing->pcmd) + in __sgx_encl_ewb()
170 backing->pcmd_offset; in __sgx_encl_ewb()
173 set_page_dirty(backing->pcmd); in __sgx_encl_ewb()
174 set_page_dirty(backing->contents); in __sgx_encl_ewb()
177 backing->pcmd_offset)); in __sgx_encl_ewb()
198 struct sgx_backing *backing) in sgx_encl_ewb() argument
216 ret = __sgx_encl_ewb(epc_page, va_slot, backing); in sgx_encl_ewb()
224 ret = __sgx_encl_ewb(epc_page, va_slot, backing); in sgx_encl_ewb()
[all …]
|
| D | encl.c | 16 struct sgx_backing *backing);
123 struct inode *inode = file_inode(encl->backing); in sgx_encl_truncate_backing_page()
736 if (encl->backing) in sgx_encl_release()
737 fput(encl->backing); in sgx_encl_release()
930 struct address_space *mapping = encl->backing->f_mapping; in sgx_encl_get_backing_page()
950 struct sgx_backing *backing) in __sgx_encl_get_backing() argument
966 backing->contents = contents; in __sgx_encl_get_backing()
967 backing->pcmd = pcmd; in __sgx_encl_get_backing()
968 backing->pcmd_offset = page_pcmd_off & (PAGE_SIZE - 1); in __sgx_encl_get_backing()
1041 struct sgx_backing *backing) in sgx_encl_alloc_backing() argument
[all …]
|
| D | encl.h | 64 struct file *backing; member
111 struct sgx_backing *backing);
112 void sgx_encl_put_backing(struct sgx_backing *backing);
|
| D | ioctl.c | 64 struct file *backing; in sgx_encl_create() local
77 backing = shmem_file_setup("SGX backing", encl_size + (encl_size >> 5), in sgx_encl_create()
79 if (IS_ERR(backing)) { in sgx_encl_create()
80 ret = PTR_ERR(backing); in sgx_encl_create()
84 encl->backing = backing; in sgx_encl_create()
126 fput(encl->backing); in sgx_encl_create()
127 encl->backing = NULL; in sgx_encl_create()
|
| /linux-6.1.9/Documentation/admin-guide/ |
| D | bcache.rst | 30 dirty data to the backing device is always done sequentially, scanning from the
48 and backing device must be formatted before use::
54 you format your backing devices and cache device at the same time, you won't
69 Registering the backing device makes the bcache device show up in /dev; you can
73 slow devices as bcache backing devices without a cache, and you can choose to add
101 After your cache device and backing device are registered, the backing device
102 must be attached to your cache set to enable caching. Attaching a backing
109 your bcache devices. If a backing device has data in a cache somewhere, the
114 can force run the backing device::
118 (You need to use /sys/block/sdb (or whatever your backing device is called), not
[all …]
|
| /linux-6.1.9/drivers/block/zram/ |
| D | Kconfig | 59 bool "Write back incompressible or idle page to backing device"
63 in memory. Instead, write it out to backing device.
64 For this feature, admin should set up backing device via
68 idle page's writeback to the backing device to save in memory.
|
| /linux-6.1.9/Documentation/usb/ |
| D | mass-storage.rst | 41 backing storage for each logical unit. There may be at most
45 *BEWARE* that if a file is used as a backing storage, it may not
53 simulating CD-ROM, block size of the device if the backing file is
64 backing file will be closed to simulate ejection and the logical
65 unit will not be mountable by the host until a new backing file is
69 If a logical unit is not removable (the default), a backing file
96 backing files.
99 backing file could not be opened in read/write mode, the gadget
163 When read it returns the path to the backing file for the given
164 logical unit. If there is no backing file (possible only if the
[all …]
|
| /linux-6.1.9/drivers/gpu/drm/gma500/ |
| D | framebuffer.c | 245 struct psb_gem_object *backing; in psbfb_create() local
264 backing = psb_gem_create(dev, size, "fb", true, PAGE_SIZE); in psbfb_create()
265 if (IS_ERR(backing)) in psbfb_create()
266 return PTR_ERR(backing); in psbfb_create()
267 obj = &backing->base; in psbfb_create()
269 memset(dev_priv->vram_addr + backing->offset, 0, size); in psbfb_create()
295 info->screen_base = dev_priv->vram_addr + backing->offset; in psbfb_create()
|
| /linux-6.1.9/fs/romfs/ |
| D | Kconfig | 20 # Select the backing stores to be supported
23 prompt "RomFS backing stores"
27 Select the backing stores to be supported.
|
| /linux-6.1.9/Documentation/admin-guide/blockdev/ |
| D | zram.rst | 203 can write out to backing device as 4KB unit
274 The bd_stat file represents a device's backing device statistics. It consists of
278 bd_count size of data written in backing device.
280 bd_reads the number of reads from backing device
282 bd_writes the number of writes to backing device
313 to backing storage rather than keeping it in memory.
314 To use the feature, admin should set up backing device via::
351 If an admin wants to write a specific page in zram device to the backing device,
428 written page to backing store
435 and the block's state is huge so it is written back to the backing
|
| /linux-6.1.9/Documentation/admin-guide/mm/ |
| D | nommu-mmap.rst | 45 - If possible, the file mapping will be directly on the backing device
46 if the backing device has the NOMMU_MAP_DIRECT capability and
50 - If the backing device can't or won't permit direct sharing,
64 the mapping's backing pages. The page is then backed by swap instead.
72 pages written back to file; writes to file reflected into pages backing
113 paged aligned in the backing store.
158 allocated if mmap() chooses not to map the backing device directly. An
211 The driver should also provide backing device information with capabilities set
260 Memory backed devices are indicated by the mapping's backing device info having
|
| /linux-6.1.9/Documentation/admin-guide/device-mapper/ |
| D | unstriped.rst | 10 without having to touch the true backing block-device. It can also be
11 used to unstripe a hardware RAID-0 to access backing disks.
39 individual backing loop devices. We write data to the newly exposed
|
| /linux-6.1.9/Documentation/mm/ |
| D | page_frags.rst | 14 network stack and network device drivers to provide a backing region of
18 In order to make use of the page fragment APIs a backing page fragment
|
| /linux-6.1.9/drivers/media/i2c/ccs/ |
| D | ccs-data.h | 224 void *backing; member
|
| /linux-6.1.9/Documentation/virt/kvm/s390/ |
| D | s390-diag.rst | 108 However, on the host the real cpu backing the vcpu may itself not be
111 the backing cpu will hopefully cause that cpu, and thus subsequently
|
| /linux-6.1.9/drivers/vfio/ |
| D | Kconfig | 39 devices without IOMMU backing for the purpose of re-using the VFIO
|
| /linux-6.1.9/Documentation/admin-guide/pm/ |
| D | intel_epb.rst | 39 level, the physical register backing it may be shared by multiple CPUs (for
|
| /linux-6.1.9/Documentation/filesystems/ |
| D | ramfs-rootfs-initramfs.rst | 20 backing store (usually the block device the filesystem is mounted on) are kept
23 written to files is marked clean as soon as it has been written to backing
28 With ramfs, there is no backing store. Files written into ramfs allocate
43 an area of RAM and used it as backing store for a filesystem. This block
68 should get written to backing store (rather than swap space), but ramfs hasn't
69 got any backing store. Because of this, only root (or a trusted user) should
|
| /linux-6.1.9/Documentation/admin-guide/LSM/ |
| D | LoadPin.rst | 18 block device backing the filesystem is not read-only, a sysctl is
|
| /linux-6.1.9/drivers/gpu/drm/i915/ |
| D | TODO.txt | 21 backing storage side.
|