Home
last modified time | relevance | path

Searched refs:reservations (Results 1 – 13 of 13) sorted by relevance

/linux/Documentation/mm/
H A Dhugetlbfs_reserv.rst62 region in the reserv_map may indicate reservations exist for the
63 range, or reservations do not exist.
68 Indicates this task is the owner of the reservations
112 was specified, then this routine returns immediately as no reservations
122 in which reservations are represented in the reservation map.
125 exists or did exist for the corresponding page. As reservations are
128 a reservation exists for the corresponding page. As reservations are
130 reservation map can also be used to determine which reservations have
135 to indicate this VMA owns the reservations.
137 The reservation map is consulted to determine how many huge page reservations
[all …]
/linux/Documentation/filesystems/
H A Docfs2.rst99 resv_level=2 (*) Set how aggressive allocation reservations will be.
100 Valid values are between 0 (reservations off) to 8
101 (maximum space for reservations).
102 dir_resv_level= (*) By default, directory reservations will scale with file
103 reservations - users should rarely need to change this
104 value. If allocation reservations are turned off, this
/linux/Documentation/arch/arm64/
H A Dkdump.rst31 For kdump reservations, low memory is the memory area under a specific
66 reservations. The user would not need to know the system memory layout
75 many systems the low memory is precious and crashkernel reservations
/linux/fs/ocfs2/
H A DMakefile31 reservations.o \
/linux/Documentation/block/
H A Dpr.rst16 All implementations are expected to ensure the reservations survive
22 The following types of reservations are supported:
/linux/Documentation/admin-guide/nfs/
H A Dpnfs-scsi-server.rst21 option and the underlying SCSI device support persistent reservations.
/linux/Documentation/filesystems/iomap/
H A Doperations.rst255 such `reservations
265 This function must *only* remove delayed allocation reservations, in
355 should throw away any reservations that may have been made for the write.
360 delalloc reservations to avoid having delalloc reservations for
H A Ddesign.rst357 They need to avoid waiting on transaction reservations to allow
387 For example, a write might wish to commit the reservations for the bytes
/linux/Documentation/bpf/
H A Dringbuf.rst179 a strict ordering between reservations. Commits, on the other hand, are
181 in the order of reservations, but only after all previous records where
/linux/fs/btrfs/
H A Dblock-group.c385 if (atomic_dec_and_test(&bg->reservations)) in btrfs_dec_block_group_reservations()
386 wake_up_var(&bg->reservations); in btrfs_dec_block_group_reservations()
412 wait_var_event(&bg->reservations, !atomic_read(&bg->reservations)); in btrfs_wait_block_group_reservations()
H A Dextent-tree.c2799 atomic_inc(&bg->reservations); in btrfs_inc_block_group_reservations()
/linux/mm/
H A Dhugetlb.c1277 struct resv_map *reservations = vma_resv_map(vma); in clear_vma_resv_huge_pages() local
1279 if (reservations && is_vma_resv_set(vma, HPAGE_RESV_OWNER)) { in clear_vma_resv_huge_pages()
1280 resv_map_put_hugetlb_cgroup_uncharge_info(reservations); in clear_vma_resv_huge_pages()
1281 kref_put(&reservations->refs, resv_map_release); in clear_vma_resv_huge_pages()
/linux/Documentation/admin-guide/
H A Dkernel-parameters.txt5174 use_e820 [X86] Use E820 reservations to exclude parts of
5179 no_e820 [X86] Ignore E820 reservations for PCI host