| /linux-4.1.27/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-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-4.1.27/drivers/gpu/drm/gma500/ |
| D | framebuffer.c | 320 struct gtt_range *backing; in psbfb_alloc() local
322 backing = psb_gtt_alloc_range(dev, aligned_size, "fb", 1, PAGE_SIZE); in psbfb_alloc()
323 if (backing) { in psbfb_alloc()
324 drm_gem_private_object_init(dev, &backing->gem, aligned_size); in psbfb_alloc()
325 return backing; in psbfb_alloc()
349 struct gtt_range *backing; in psbfb_create() local
375 backing = psbfb_alloc(dev, size); in psbfb_create()
382 } while (backing == NULL && pitch_lines <= 16); in psbfb_create()
387 if (backing == NULL) { in psbfb_create()
403 backing = psbfb_alloc(dev, size); in psbfb_create()
[all …]
|
| /linux-4.1.27/Documentation/ |
| D | bcache.txt | 22 dirty data to the backing device is always done sequentially, scanning from the
40 and backing device must be formatted before use.
45 you format your backing devices and cache device at the same time, you won't
55 Registering the backing device makes the bcache device show up in /dev; you can
82 After your cache device and backing device are registered, the backing device
83 must be attached to your cache set to enable caching. Attaching a backing
90 your bcache devices. If a backing device has data in a cache somewhere, the
95 can force run the backing device:
99 (You need to use /sys/block/sdb (or whatever your backing device is called), not
103 The backing device will still use that cache set if it shows up in the future,
[all …]
|
| D | dma-buf-sharing.txt | 21 - decides about the actual backing storage where this allocation happens,
111 allocate the backing storage for this buffer, but wait for the first buffer-user
138 of the attached devices, and choose an appropriate backing storage for the
197 The attach-detach calls allow the exporter to figure out backing-storage
203 to allow just-in-time backing of storage, and migration mid-way through a
206 - Migration of backing storage if needed
209 - and the backing storage has been allocated for this buffer,
214 if the new buffer-user has stricter 'backing-storage constraints', and the
219 exporter could potentially move the buffer to the stricter backing-storage,
221 from the migrated backing-storage.
[all …]
|
| 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 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
114 paged aligned in the backing store.
159 allocated if mmap() chooses not to map the backing device directly. An
216 The driver should also provide backing device information with capabilities set
266 Memory backed devices are indicated by the mapping's backing device info having
|
| D | cachetlb.txt | 63 The "vma" is the backing store being used for the region.
75 from the TLB. The 'vma' is the backing structure used by
175 The "vma" is the backing store being used for the region.
187 from the cache. The 'vma' is the backing structure used by
|
| D | workqueue.txt | 97 number of these backing pools is dynamic.
137 For unbound workqueues, the number of backing pools is dynamic.
140 backing worker pools matching the attributes. The responsibility of
|
| /linux-4.1.27/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 …]
|
| D | gadget-testing.txt | 275 file - The path to the backing file for the LUN.
|
| /linux-4.1.27/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-4.1.27/fs/exofs/ |
| D | Kconfig | 6 as its backing storage.
|
| /linux-4.1.27/Documentation/vm/ |
| D | zswap.txt | 25 Zswap evicts pages from compressed cache on an LRU basis to the backing swap
36 the backing swap device in the case that the compressed pool is full.
|
| D | frontswap.txt | 13 a "backing" store for a swap device. The storage is assumed to be
|
| D | transhuge.txt | 8 using huge pages for the backing of virtual memory with huge pages
|
| D | numa_memory_policy.txt | 124 file mapping. Rather, shared page cache pages, including pages backing
|
| /linux-4.1.27/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 | 268 This is called by FS-Cache to indicate that a backing store is being
429 The cache will return -ENOBUFS if there is no backing cache or if there is no
492 backing device directly into the page specified.
574 (2) The function will submit a request to write the data to cache's backing
748 invalidate its state; allocate, read or write backing pages - though it is
759 invalidates any backing objects and waits for cessation of activity on any
774 cookie, will begin the procedure of acquiring backing objects.
780 as enabled if provisional backing objects are allocated.
|
| D | cachefiles.txt | 42 filesystem providing the backing services. Note that CacheFiles does not
470 LOOKUPS Length of time to perform a lookup on the backing fs
471 MKDIRS Length of time to perform a mkdir on the backing fs
472 CREATES Length of time to perform a create on the backing fs
|
| D | backend-api.txt | 148 is backing. An object should retired when put_object() is called if it is
356 This is called to ask the backend to synchronise a cache with its backing
414 reserve a backing block if not. FS-Cache will have done as much checking
418 backend managed to reserve a backing block; -ENOBUFS or -ENOMEM if it
480 If there's no backing block available, then -ENOBUFS should be returned
|
| D | object.txt | 308 The event selected depends on whether the netfs asks for the backing
|
| /linux-4.1.27/drivers/staging/android/ |
| D | Kconfig | 47 syncrhronization. Useful when there is no hardware primitive backing
|
| /linux-4.1.27/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
|
| D | Locking | 332 files backing (non block device backed) swapfiles. A return value
334 backing swapspace. The swapspace operations will be proxied to the
|
| D | vfat.txt | 176 configuration, determined by backing device size. These static
|
| D | vfs.txt | 605 writepage: called by the VM to write a dirty page to backing store.
623 readpage: called by the VM to read a page from backing store.
|
| D | proc.txt | 539 size, in KB, that is backing the mapping up.
|
| /linux-4.1.27/mm/ |
| D | Makefile | 20 util.o mmzone.o vmstat.o backing-dev.o \
|
| D | Kconfig | 485 of a "backing" store for a swap device. The data is stored into
|
| /linux-4.1.27/drivers/gpu/drm/i915/ |
| D | Kconfig | 9 # we need shmfs for the swappable backing store, and in particular
|
| /linux-4.1.27/Documentation/video4linux/bttv/ |
| D | PROBLEMS | 51 Disable backing store by starting X with the option "-bs"
|
| /linux-4.1.27/Documentation/devicetree/bindings/soc/fsl/ |
| D | bman.txt | 67 BMan requires a contiguous range of physical memory used for the backing store
|
| D | qman.txt | 75 QMan requires two contiguous range of physical memory used for the backing store
|
| /linux-4.1.27/net/irda/ |
| D | Kconfig | 75 start backing-off before sending another RR frame, waiting longer
|
| /linux-4.1.27/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 62 7.5 uml_moo : Merging a COW file with its backing file
1894 The name of the backing file is stored in the COW file header, so it
1905 Here is a 'ls -l' of a COW file and backing file from one boot and
1931 Once a filesystem is being used as a readonly backing file for a COW
1934 of the backing file are stored in the COW file header at its creation,
1942 backing file or the COW header by hand, you will get a corrupted
1949 backing file and expecting that all of the COW files using it will see
1955 7.5. uml_moo : Merging a COW file with its backing file
1958 merge the changes in the COW file into the backing file every once in
1967 host% uml_moo COW file new backing file
[all …]
|
| /linux-4.1.27/Documentation/device-mapper/ |
| D | snapshot.txt | 28 Reads will be mapped directly to the backing device. For each write, the
|
| /linux-4.1.27/fs/ |
| D | Kconfig | 167 hugetlbfs is a filesystem backing for HugeTLB pages, based on
|
| /linux-4.1.27/drivers/block/ |
| D | Kconfig | 404 and will prevent RAM block device backing store memory from being
|
| /linux-4.1.27/Documentation/filesystems/configfs/ |
| D | configfs.txt | 33 kernel modules backing the items must respond to this.
|
| /linux-4.1.27/Documentation/laptops/ |
| D | thinkpad-acpi.txt | 959 mode with NVRAM backing (so that brightness changes are remembered across
1121 selects EC mode, and volume_mode=3 selects EC mode with NVRAM backing
|
| /linux-4.1.27/scripts/kconfig/ |
| D | zconf.lex.c_shipped | 259 * possible backing-up.
|
| /linux-4.1.27/scripts/genksyms/ |
| D | lex.lex.c_shipped | 240 * possible backing-up.
|
| /linux-4.1.27/scripts/dtc/ |
| D | dtc-lexer.lex.c_shipped | 250 * possible backing-up.
|
| /linux-4.1.27/Documentation/virtual/kvm/ |
| D | api.txt | 930 When the KVM_CAP_SYNC_MMU capability is available, changes in the backing of
2227 When that flag is set, guest page sizes must "fit" the backing
|
| /linux-4.1.27/lib/ |
| D | Kconfig.debug | 1120 the memory backing the kobject can be immediately freed. This
|
| /linux-4.1.27/ |
| D | CREDITS | 1660 D: Mods to loop device to support sparse backing files
|