Home
last modified time | relevance | path

Searched refs:backing (Results 1 – 25 of 98) sorted by relevance

1234

/linux/Documentation/ABI/testing/
H A Dsysfs-block-bcache5 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 …]
H A Dconfigfs-usb-gadget-mass-storage23 file The path to the backing file for the LUN.
36 the function is active. It causes the backing
H A Dsysfs-block-loop15 (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
H A Dsysfs-block-zram90 The backing_dev file is read-write and set up backing
107 huge page writeback to backing device.
113 The bd_stat file is read-only and represents backing device's
H A Dsysfs-class-bdi23 The default backing dev, used for non-block device backed
131 If set, the backing device requires that all pages comprising a write
/linux/drivers/gpu/drm/gma500/
H A Dfbdev.c116 struct psb_gem_object *backing; in psb_fbdev_driver_fbdev_probe() local
153 backing = psb_gem_create(dev, size, "fb", true, PAGE_SIZE); in psb_fbdev_driver_fbdev_probe()
154 if (IS_ERR(backing)) in psb_fbdev_driver_fbdev_probe()
155 return PTR_ERR(backing); in psb_fbdev_driver_fbdev_probe()
156 obj = &backing->base; in psb_fbdev_driver_fbdev_probe()
173 info->screen_base = dev_priv->vram_addr + backing->offset; in psb_fbdev_driver_fbdev_probe()
178 info->fix.smem_start = dev_priv->stolen_base + backing->offset; in psb_fbdev_driver_fbdev_probe()
/linux/arch/x86/kernel/cpu/sgx/
H A Dmain.c164 struct sgx_backing *backing) in __sgx_encl_ewb() argument
172 pginfo.contents = (unsigned long)kmap_local_page(backing->contents); in __sgx_encl_ewb()
173 pginfo.metadata = (unsigned long)kmap_local_page(backing->pcmd) + in __sgx_encl_ewb()
174 backing->pcmd_offset; in __sgx_encl_ewb()
177 set_page_dirty(backing->pcmd); in __sgx_encl_ewb()
178 set_page_dirty(backing->contents); in __sgx_encl_ewb()
181 backing->pcmd_offset)); in __sgx_encl_ewb()
202 struct sgx_backing *backing) in sgx_encl_ewb() argument
220 ret = __sgx_encl_ewb(epc_page, va_slot, backing); in sgx_encl_ewb()
228 ret = __sgx_encl_ewb(epc_page, va_slot, backing); in sgx_encl_ewb()
[all …]
H A Dencl.c16 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()
953 struct address_space *mapping = encl->backing->f_mapping; in sgx_encl_get_backing_page()
973 struct sgx_backing *backing) in __sgx_encl_get_backing() argument
989 backing->contents = contents; in __sgx_encl_get_backing()
990 backing->pcmd = pcmd; in __sgx_encl_get_backing()
991 backing->pcmd_offset = page_pcmd_off & (PAGE_SIZE - 1); in __sgx_encl_get_backing()
1064 struct sgx_backing *backing) in sgx_encl_alloc_backing() argument
[all …]
H A Dencl.h64 struct file *backing; member
111 struct sgx_backing *backing);
112 void sgx_encl_put_backing(struct sgx_backing *backing);
H A Dioctl.c65 struct file *backing; in sgx_encl_create() local
85 backing = shmem_file_setup("SGX backing", encl_size + (encl_size >> 5), in sgx_encl_create()
87 if (IS_ERR(backing)) { in sgx_encl_create()
88 ret = PTR_ERR(backing); in sgx_encl_create()
92 encl->backing = backing; in sgx_encl_create()
134 fput(encl->backing); in sgx_encl_create()
135 encl->backing = NULL; in sgx_encl_create()
/linux/Documentation/filesystems/fuse/
H A Dfuse-passthrough.rst15 "backing file".
18 the backing file on a lower filesystem) with the FUSE kernel module. The kernel
19 then receives an identifier (``backing_id``) for this registered backing file.
40 backing file descriptor and obtain a ``backing_id``.
46 the ``backing_id`` to release the kernel's reference to the backing file
62 descriptor to a backing file and registering it with the FUSE kernel module via
65 reference to the backing ``struct file``.
68 descriptor to the backing file after registration. The kernel, however, will
76 daemon closes its file descriptor, the open backing file held by the kernel
85 (``RLIMIT_NOFILE``). If an unprivileged daemon could register backing files
[all …]
/linux/Documentation/admin-guide/
H A Dbcache.rst29 dirty data to the backing device is always done sequentially, scanning from the
47 and backing device must be formatted before use::
53 you format your backing devices and cache device at the same time, you won't
68 Registering the backing device makes the bcache device show up in /dev; you can
72 slow devices as bcache backing devices without a cache, and you can choose to add
100 After your cache device and backing device are registered, the backing device
101 must be attached to your cache set to enable caching. Attaching a backing
108 your bcache devices. If a backing device has data in a cache somewhere, the
113 can force run the backing device::
117 (You need to use /sys/block/sdb (or whatever your backing device is called), not
[all …]
/linux/Documentation/admin-guide/blockdev/
H A Dzoned_loop.rst19 device using one regular file per zone as backing storage. This driver does not
26 size. The size of a file backing a conventional zone is always equal to the zone
27 size. The size of a file backing a sequential zone indicates the amount of data
31 When resetting a sequential zone, its backing file size is truncated to zero.
32 Conversely, for a zone finish operation, the backing file is truncated to the
35 backing file system. Of course, for such configuration, writing more data than
36 the storage space available on the backing file system will result in write
127 base directory containing the backing files of the device zones must be deleted.
139 For the device created (/dev/zloop0), the zone backing files are all created
179 the device was first created. To fully delete a zoned device, its backing files
H A Dzram.rst215 can write out to backing device as 4KB unit
287 The bd_stat file represents a device's backing device statistics. It consists of
291 bd_count size of data written in backing device.
293 bd_reads the number of reads from backing device
295 bd_writes the number of writes to backing device
346 to backing storage rather than keeping it in memory.
347 To use the feature, admin should set up backing device via::
372 If an admin wants to write a specific page in zram device to the backing device,
441 writing it to the backing device. This behavior can be changed by enabling
443 to the backing device, thus avoiding decompression overhead. To enable
[all …]
/linux/Documentation/usb/
H A Dmass-storage.rst41 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/tools/testing/selftests/mm/
H A Dguard-regions.c56 enum backing_type backing; in FIXTURE_VARIANT() local
61 .backing = ANON_BACKED, in FIXTURE_VARIANT_ADD()
66 .backing = SHMEM_BACKED, in FIXTURE_VARIANT_ADD()
71 .backing = LOCAL_FILE_BACKED, in FIXTURE_VARIANT_ADD()
76 switch (variant->backing) { in is_anon_backed()
93 switch (variant->backing) { in mmap_()
281 if (variant->backing != LOCAL_FILE_BACKED) in local_fs_has_sane_mmap()
317 switch (variant->backing) { in FIXTURE_SETUP()
336 if (variant->backing == ANON_BACKED) in FIXTURE_TEARDOWN_PARENT()
918 switch (variant->backing) { in TEST_F()
[all …]
/linux/fs/romfs/
H A DKconfig20 # Select the backing stores to be supported
23 prompt "RomFS backing stores"
27 Select the backing stores to be supported.
/linux/drivers/block/zram/
H A DKconfig108 bool "Write back incompressible or idle page to backing device"
112 back to a backing device, helping save memory.
113 For this feature, admin should set up backing device via
117 idle page's writeback to the backing device to save in memory.
/linux/Documentation/admin-guide/mm/
H A Dnommu-mmap.rst45 - 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/admin-guide/device-mapper/
H A Dunstriped.rst10 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
H A Ddelay.rst52 # onto the same backing device at offset 0 sectors.
/linux/Documentation/mm/
H A Dpage_frags.rst12 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/fs/fuse/
H A DMakefile17 fuse-$(CONFIG_FUSE_PASSTHROUGH) += passthrough.o backing.o
/linux/Documentation/filesystems/
H A Dramfs-rootfs-initramfs.rst19 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/drivers/media/i2c/ccs/
H A Dccs-data.h224 void *backing; member

1234