| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-6.6/Documentation/usb/ |
| D | mass-storage.rst | 10 multiple logical units (LUNs). Backing storage for each LUN is
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/usb/ |
| D | mass-storage.rst | 10 multiple logical units (LUNs). Backing storage for each LUN is
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
[all …]
|
| /kernel/linux/linux-6.6/arch/x86/kernel/cpu/sgx/ |
| D | encl.c | 16 struct sgx_backing *backing);
37 * The backing storage to which enclave pages are reclaimed is laid out as
92 * to ensure that the page is not already in backing store. in reclaimer_writing_to_pcmd()
106 * follow right after the EPC data in the backing storage. In addition to the
119 * Free a page from the backing storage in the given page index.
123 struct inode *inode = file_inode(encl->backing); in sgx_encl_truncate_backing_page()
320 * When an initialized enclave accesses a page with no backing EPC page
756 if (encl->backing) in sgx_encl_release()
757 fput(encl->backing); in sgx_encl_release()
952 struct address_space *mapping = encl->backing->f_mapping; in sgx_encl_get_backing_page()
[all …]
|
| D | main.c | 160 struct sgx_backing *backing) in __sgx_encl_ewb() argument
168 pginfo.contents = (unsigned long)kmap_local_page(backing->contents); in __sgx_encl_ewb()
169 pginfo.metadata = (unsigned long)kmap_local_page(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 …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/gma500/ |
| D | framebuffer.c | 204 * @gt: backing object
242 * @gt: the backing object
284 struct gtt_range *backing; in psbfb_alloc() local
285 /* Begin by trying to use stolen memory backing */ in psbfb_alloc()
286 backing = psb_gtt_alloc_range(dev, aligned_size, "fb", 1, PAGE_SIZE); in psbfb_alloc()
287 if (backing) { in psbfb_alloc()
288 drm_gem_private_object_init(dev, &backing->gem, aligned_size); in psbfb_alloc()
289 return backing; in psbfb_alloc()
311 struct gtt_range *backing; in psbfb_create() local
336 /* Allocate the fb in the GTT with stolen page backing */ in psbfb_create()
[all …]
|
| /kernel/linux/linux-5.10/drivers/block/zram/ |
| D | Kconfig | 18 bool "Write back incompressible or idle page to backing device"
22 in memory. Instead, write it out to backing device.
23 For this feature, admin should set up backing device via
27 idle page's writeback to the backing device to save in memory.
|
| /kernel/linux/linux-6.6/drivers/md/bcache/ |
| D | bcache_ondisk.h | 140 * Version 1: Backing device
143 * Version 4: Backing device with data offset
198 /* Backing devices */
203 * backing devices, so don't add anything here until we fix
204 * things to not need it for backing devices anymore
257 /* Backing devices */
262 * backing devices, so don't add anything here until we fix
263 * things to not need it for backing devices anymore
385 /* UUIDS - per backing device/flash only volume metadata */
435 /* UUIDS - per backing device/flash only volume metadata */
|
| /kernel/linux/linux-5.10/include/uapi/linux/ |
| D | bcache.h | 139 * Version 1: Backing device
142 * Version 4: Backing device with data offset
197 /* Backing devices */
202 * backing devices, so don't add anything here until we fix
203 * things to not need it for backing devices anymore
256 /* Backing devices */
261 * backing devices, so don't add anything here until we fix
262 * things to not need it for backing devices anymore
384 /* UUIDS - per backing device/flash only volume metadata */
434 /* UUIDS - per backing device/flash only volume metadata */
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/intel/i40e/ |
| D | i40e_hmc.c | 48 /* allocate a 4K pd page or 2M backing page */ in i40e_add_sd_table_entry()
74 /* Increment backing page reference count */ in i40e_add_sd_table_entry()
136 /* allocate a 4K backing page */ in i40e_add_pd_table_entry()
154 /* Add the backing page physical address in the pd entry */ in i40e_add_pd_table_entry()
167 * i40e_remove_pd_bp - remove a backing page from a page descriptor
175 * 2. Write to register PMPDINV to invalidate the backing page in FV cache
178 * 1. Caller can deallocate the memory used by backing storage after this
233 * i40e_prep_remove_sd_bp - Prepares to remove a backing page from a sd entry
259 * i40e_remove_sd_bp_new - Removes a backing page from a segment descriptor
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/intel/i40e/ |
| D | i40e_hmc.c | 55 /* allocate a 4K pd page or 2M backing page */ in i40e_add_sd_table_entry()
81 /* Increment backing page reference count */ in i40e_add_sd_table_entry()
143 /* allocate a 4K backing page */ in i40e_add_pd_table_entry()
161 /* Add the backing page physical address in the pd entry */ in i40e_add_pd_table_entry()
174 * i40e_remove_pd_bp - remove a backing page from a page descriptor
182 * 2. Write to register PMPDINV to invalidate the backing page in FV cache
185 * 1. Caller can deallocate the memory used by backing storage after this
240 * i40e_prep_remove_sd_bp - Prepares to remove a backing page from a sd entry
266 * i40e_remove_sd_bp_new - Removes a backing page from a segment descriptor
|
| D | i40e_lan_hmc.c | 33 * @txq_num: number of Tx queues needing backing context
34 * @rxq_num: number of Rx queues needing backing context
35 * @fcoe_cntx_num: amount of FCoE statefull contexts needing backing context
36 * @fcoe_filt_num: number of FCoE filters needing backing context
64 * @txq_num: number of Tx queues needing backing context
65 * @rxq_num: number of Rx queues needing backing context
66 * @fcoe_cntx_num: amount of FCoE statefull contexts needing backing context
67 * @fcoe_filt_num: number of FCoE filters needing backing context
226 * 2. write to register PMPDINV to invalidate the backing page in FV cache
245 * i40e_remove_sd_bp - remove a backing page from a segment descriptor
[all …]
|
| /kernel/linux/linux-5.10/fs/cachefiles/ |
| D | rdwr.c | 17 * - we use this to detect read completion of backing pages
149 * copy data from backing pages to netfs pages to complete a read operation
195 "Readpage failed on backing file %lx", in cachefiles_read_copier()
226 * read the corresponding page to the given set from the backing file
252 /* attempt to get hold of the backing page */ in cachefiles_read_backing_file_one()
275 /* we've installed a new backing page, so now we need to start in cachefiles_read_backing_file_one()
309 /* if the backing page is already present, it can be in one of in cachefiles_read_backing_file_one()
330 /* the backing page is already up to date, attach the netfs in cachefiles_read_backing_file_one()
362 cachefiles_io_error_obj(object, "Page read error on backing file"); in cachefiles_read_backing_file_one()
440 /* submit the apparently valid page to the backing fs to be in cachefiles_read_or_alloc_page()
[all …]
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/gma500/ |
| D | fbdev.c | 161 struct psb_gem_object *backing; in psb_fbdev_fb_probe() local
197 /* Allocate the framebuffer in the GTT with stolen page backing */ in psb_fbdev_fb_probe()
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()
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/ |
| D | drm_gem_framebuffer_helper.c | 35 * &drm_framebuffer and use &drm_gem_object for their backing storage.
43 * drm_gem_fb_get_obj() - Get GEM object backing the framebuffer
89 * Frees a GEM backed framebuffer with its backing buffer(s) and the structure
111 * This function creates a handle for the GEM object backing the framebuffer.
133 * @file: DRM file that holds the GEM handle(s) backing the framebuffer
203 * @file: DRM file that holds the GEM handle(s) backing the framebuffer
245 * @file: DRM file that holds the GEM handle(s) backing the framebuffer
250 * backing the framebuffer.
282 * @file: DRM file that holds the GEM handle(s) backing the framebuffer
287 * backing the framebuffer. drm_atomic_helper_dirtyfb() is used for the dirty
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/include/xen/ |
| D | xen-front-pgdir-shbuf.h | 35 /* Page directory backing storage. */
44 * Backing storage of the shared buffer: these are the pages being
61 /* Number of pages of the buffer backing storage. */
|
| /kernel/linux/linux-5.10/include/xen/ |
| D | xen-front-pgdir-shbuf.h | 35 /* Page directory backing storage. */
44 * Backing storage of the shared buffer: these are the pages being
61 /* Number of pages of the buffer backing storage. */
|