| /Linux-v4.19/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 | 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
54 If set, the backing device requires that all pages comprising a write
|
| D | configfs-usb-gadget-mass-storage | 20 file - The path to the backing file for the LUN.
|
| /Linux-v4.19/drivers/gpu/drm/gma500/ |
| D | framebuffer.c | 298 struct gtt_range *backing; in psbfb_alloc() local
300 backing = psb_gtt_alloc_range(dev, aligned_size, "fb", 1, PAGE_SIZE); in psbfb_alloc()
301 if (backing) { in psbfb_alloc()
302 drm_gem_private_object_init(dev, &backing->gem, aligned_size); in psbfb_alloc()
303 return backing; in psbfb_alloc()
326 struct gtt_range *backing; in psbfb_create() local
352 backing = psbfb_alloc(dev, size); in psbfb_create()
359 } while (backing == NULL && pitch_lines <= 16); in psbfb_create()
364 if (backing == NULL) { in psbfb_create()
380 backing = psbfb_alloc(dev, size); in psbfb_create()
[all …]
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | bcache.rst | 27 dirty data to the backing device is always done sequentially, scanning from the
45 and backing device must be formatted before use::
51 you format your backing devices and cache device at the same time, you won't
62 Registering the backing device makes the bcache device show up in /dev; you can
66 slow devices as bcache backing devices without a cache, and you can choose to add
94 After your cache device and backing device are registered, the backing device
95 must be attached to your cache set to enable caching. Attaching a backing
102 your bcache devices. If a backing device has data in a cache somewhere, the
107 can force run the backing device::
111 (You need to use /sys/block/sdb (or whatever your backing device is called), not
[all …]
|
| /Linux-v4.19/drivers/block/zram/ |
| D | Kconfig | 19 bool "Write back incompressible page to backing device"
24 in memory. Instead, write it out to backing device.
25 For this feature, admin should set up backing device via
|
| /Linux-v4.19/Documentation/usb/ |
| D | mass-storage.txt | 35 backing storage for each logical unit. There may be at most
39 *BEWARE* that if a file is used as a backing storage, it may not
47 simulating CD-ROM, block size of the device if the backing file is
58 backing file will be closed to simulate ejection and the logical
59 unit will not be mountable by the host until a new backing file is
63 If a logical unit is not removable (the default), a backing file
90 backing files.
93 backing file could not be opened in read/write mode, the gadget
156 When read it returns the path to the backing file for the given
157 logical unit. If there is no backing file (possible only if the
[all …]
|
| /Linux-v4.19/fs/romfs/ |
| D | Kconfig | 19 # Select the backing stores to be supported
22 prompt "RomFS backing stores"
26 Select the backing stores to be supported.
|
| D | storage.c | 18 #error no ROMFS backing store interface configured
|
| /Linux-v4.19/Documentation/ |
| D | nommu-mmap.txt | 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-v4.19/Documentation/device-mapper/ |
| D | unstriped.txt | 6 without having to touch the true backing block-device. It can also be
7 used to unstripe a hardware RAID-0 to access backing disks.
35 individual backing loop devices. We write data to the newly exposed
|
| /Linux-v4.19/fs/exofs/ |
| D | Kconfig | 6 as its backing storage.
|
| /Linux-v4.19/Documentation/vm/ |
| 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
|
| D | zswap.rst | 34 Zswap evicts pages from compressed cache on an LRU basis to the backing swap
60 the backing swap device in the case that the compressed pool is full.
|
| /Linux-v4.19/drivers/dma-buf/ |
| D | Kconfig | 27 synchronization. Useful when there is no hardware primitive backing
|
| /Linux-v4.19/Documentation/admin-guide/LSM/ |
| D | LoadPin.rst | 18 block device backing the filesystem is not read-only, a sysctl is
|
| /Linux-v4.19/Documentation/filesystems/caching/ |
| D | operations.txt | 83 the backing filesystem in CacheFiles. Although readpages() does an
100 This is, for example, used by CacheFiles to copy data from a backing fs
101 page to a netfs page after the backing fs has read the page in.
|
| D | netfs-api.txt | 230 This is called by FS-Cache to indicate that a backing store is being
409 The cache will return -ENOBUFS if there is no backing cache or if there is no
471 backing device directly into the page specified.
554 (2) The function will submit a request to write the data to cache's backing
730 invalidate its state; allocate, read or write backing pages - though it is
742 invalidates any backing objects and waits for cessation of activity on any
759 cookie, will begin the procedure of acquiring backing objects.
765 as enabled if provisional backing objects are allocated.
|
| /Linux-v4.19/drivers/vfio/ |
| D | Kconfig | 39 devices without IOMMU backing for the purpose of re-using the VFIO
|
| /Linux-v4.19/Documentation/blockdev/ |
| D | zram.txt | 242 to backing storage rather than keeping it in memory.
243 User should set up backing device via /sys/block/zramX/backing_dev
262 w: written page to backing store
266 and the block's state is huge so it is written back to the backing
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | ramfs-rootfs-initramfs.txt | 14 backing store (usually the block device the filesystem is mounted on) are kept
17 written to files is marked clean as soon as it has been written to backing
22 With ramfs, there is no backing store. Files written into ramfs allocate
37 an area of RAM and used it as backing store for a filesystem. This block
62 should get written to backing store (rather than swap space), but ramfs hasn't
63 got any backing store. Because of this, only root (or a trusted user) should
|
| /Linux-v4.19/mm/ |
| D | Makefile | 38 util.o mmzone.o vmstat.o backing-dev.o \
|
| /Linux-v4.19/Documentation/admin-guide/mm/ |
| D | concepts.rst | 86 hugetlbfs. It is a pseudo filesystem that uses RAM as its backing
138 is placed in the page cache and eventually gets into the backing
190 they contain is available elsewhere, or evict to the backing storage
|
| /Linux-v4.19/Documentation/devicetree/bindings/soc/fsl/ |
| D | bman.txt | 67 BMan requires a contiguous range of physical memory used for the backing store
|
