| /linux/Documentation/ABI/testing/ |
| A 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
82 For backing devices: In writeback mode, when dirty data is
84 backing device, writeback from cache to backing device starts
[all …]
|
| A 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
|
| A 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
|
| A 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
|
| A D | sysfs-class-bdi | 23 The default backing dev, used for non-block device backed
131 If set, the backing device requires that all pages comprising a write
|
| /linux/arch/x86/kernel/cpu/sgx/ |
| A D | main.c | 161 struct sgx_backing *backing) in __sgx_encl_ewb() argument
171 backing->pcmd_offset; in __sgx_encl_ewb()
174 set_page_dirty(backing->pcmd); in __sgx_encl_ewb()
175 set_page_dirty(backing->contents); in __sgx_encl_ewb()
178 backing->pcmd_offset)); in __sgx_encl_ewb()
199 struct sgx_backing *backing) in sgx_encl_ewb() argument
252 struct sgx_backing *backing) in sgx_reclaimer_write() argument
261 sgx_encl_ewb(epc_page, backing); in sgx_reclaimer_write()
264 sgx_encl_put_backing(backing); in sgx_reclaimer_write()
300 struct sgx_backing backing[SGX_NR_TO_SCAN]; in sgx_reclaim_pages() local
[all …]
|
| A D | encl.c | 16 struct sgx_backing *backing);
123 struct inode *inode = file_inode(encl->backing); in sgx_encl_truncate_backing_page()
756 if (encl->backing) in sgx_encl_release()
757 fput(encl->backing); in sgx_encl_release()
972 struct sgx_backing *backing) in __sgx_encl_get_backing() argument
988 backing->contents = contents; in __sgx_encl_get_backing()
989 backing->pcmd = pcmd; in __sgx_encl_get_backing()
1063 struct sgx_backing *backing) in sgx_encl_alloc_backing() argument
1095 struct sgx_backing *backing) in sgx_encl_lookup_backing() argument
1106 put_page(backing->pcmd); in sgx_encl_put_backing()
[all …]
|
| A D | encl.h | 64 struct file *backing; member
111 struct sgx_backing *backing);
112 void sgx_encl_put_backing(struct sgx_backing *backing);
|
| A 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/drivers/gpu/drm/gma500/ |
| A D | fbdev.c | 161 struct psb_gem_object *backing; in psb_fbdev_fb_probe() local
198 backing = psb_gem_create(dev, size, "fb", true, PAGE_SIZE); in psb_fbdev_fb_probe()
199 if (IS_ERR(backing)) in psb_fbdev_fb_probe()
200 return PTR_ERR(backing); in psb_fbdev_fb_probe()
201 obj = &backing->base; in psb_fbdev_fb_probe()
220 info->screen_base = dev_priv->vram_addr + backing->offset; in psb_fbdev_fb_probe()
225 info->fix.smem_start = dev_priv->stolen_base + backing->offset; in psb_fbdev_fb_probe()
|
| /linux/Documentation/admin-guide/ |
| A D | bcache.rst | 48 and backing device must be formatted before use::
101 After your cache device and backing device are registered, the backing device
114 can force run the backing device::
133 the backing devices to passthrough mode.
136 backing device.
233 start backing device with missing cache::
403 Sysfs - backing device
462 backing device has likely been corrupted.
488 Sysfs - backing device stats
520 Symlink to each of the attached backing devices.
[all …]
|
| /linux/Documentation/usb/ |
| A 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
176 be read any time, and written to when there is no backing file
[all …]
|
| /linux/fs/romfs/ |
| A D | Kconfig | 20 # Select the backing stores to be supported
23 prompt "RomFS backing stores"
27 Select the backing stores to be supported.
|
| /linux/drivers/block/zram/ |
| A D | Kconfig | 107 bool "Write back incompressible or idle page to backing device"
111 back to a backing device, helping save memory.
112 For this feature, admin should set up backing device via
116 idle page's writeback to the backing device to save in memory.
|
| /linux/Documentation/admin-guide/mm/ |
| A 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/Documentation/devicetree/bindings/soc/fsl/ |
| A D | fsl,qman-fqd.yaml | 13 QMan requires two contiguous range of physical memory used for the backing store
17 BMan requires a contiguous range of physical memory used for the backing store
|
| /linux/Documentation/admin-guide/device-mapper/ |
| A 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
|
| A D | delay.rst | 52 # onto the same backing device at offset 0 sectors.
|
| /linux/Documentation/admin-guide/blockdev/ |
| A D | zram.rst | 227 can write out to backing device as 4KB unit
299 The bd_stat file represents a device's backing device statistics. It consists of
303 bd_count size of data written in backing device.
305 bd_reads the number of reads from backing device
307 bd_writes the number of writes to backing device
338 to backing storage rather than keeping it in memory.
339 To use the feature, admin should set up backing device via::
381 If an admin wants to write a specific page in zram device to the backing device,
549 written page to backing store
560 and the block's state is huge so it is written back to the backing
|
| /linux/Documentation/mm/ |
| A D | page_frags.rst | 12 network stack and network device drivers to provide a backing region of
16 In order to make use of the page fragment APIs a backing page fragment
|
| /linux/drivers/media/i2c/ccs/ |
| A D | ccs-data.h | 224 void *backing; member
|
| /linux/Documentation/virt/kvm/s390/ |
| A 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/Documentation/admin-guide/pm/ |
| A D | intel_epb.rst | 39 level, the physical register backing it may be shared by multiple CPUs (for
|
| /linux/Documentation/filesystems/ |
| A D | ramfs-rootfs-initramfs.rst | 19 backing store (usually the block device the filesystem is mounted on) are kept
22 written to files is marked clean as soon as it has been written to backing
27 With ramfs, there is no backing store. Files written into ramfs allocate
42 an area of RAM and used it as backing store for a filesystem. This block
67 should get written to backing store (rather than swap space), but ramfs hasn't
68 got any backing store. Because of this, only root (or a trusted user) should
|
| /linux/Documentation/admin-guide/LSM/ |
| A D | LoadPin.rst | 18 block device backing the filesystem is not read-only, a sysctl is
|