| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | hugetlb.rst | 24 hugetlb.<hugepagesize>.rsvd.limit_in_bytes # set/show limit of "hugepagesize" hugetlb reservations
25 hugetlb.<hugepagesize>.rsvd.max_usage_in_bytes # show max "hugepagesize" hugetlb reservations and no-reserve faults
26 hugetlb.<hugepagesize>.rsvd.usage_in_bytes # show current reservations and no-reserve faults for "hugepagesize" hugetlb
94 The HugeTLB controller allows to limit the HugeTLB reservations per control
127 When a HugeTLB cgroup goes offline with some reservations or faults still
134 reservations charged to it, that cgroup persists as a zombie until all HugeTLB
135 reservations are uncharged. HugeTLB reservations behave in this manner to match
137 memory is uncharged. Also, the tracking of HugeTLB reservations is a bit more
139 harder to reparent reservations a
[all...] |
| /linux/Documentation/mm/ |
| H A D | hugetlbfs_reserv.rst | 62 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 D | ocfs2.rst | 99 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
|
| H A D | resctrl.rst | 1204 end up allocating the same bits so the reservations are shared instead of
|
| /linux/Documentation/arch/arm64/ |
| H A D | kdump.rst | 31 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 D | Makefile | 31 reservations.o \
|
| /linux/Documentation/block/ |
| H A D | pr.rst | 16 All implementations are expected to ensure the reservations survive
22 The following types of reservations are supported:
|
| /linux/Documentation/admin-guide/nfs/ |
| H A D | pnfs-scsi-server.rst | 21 option and the underlying SCSI device support persistent reservations.
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-delayed-logging-design.rst | 16 transaction reservations are structured and accounted, and then move into how we
18 reservations bounds. At this point we need to explain how relogging works. With
59 transactions. Permanent transaction reservations can take reservations that span
65 modifications, but one-shot reservations cannot be used for permanent
156 journal. This is achieved by the transaction reservations that are made when
157 a transaction is first allocated. For permanent transactions, these reservations
166 of the btree. As such, the reservations are quite complex because we have to
204 reservations. That multiple is defined by the reservation log count, and this
233 reservations currentl
[all...] |
| H A D | xfs-online-fsck-design.rst | 1659 This reduces the worst case size of transaction reservations by breaking the
2449 reservations pin the tail of the ondisk log.
2534 clean up the space reservations that were made for the new btree, and reap the
2545 b. For unclaimed portions of incore reservations, create a regular deferred
2793 The space reservations used to create the new metadata can be used here if
3065 which are key to enabling resource reservations for active transactions.
4275 must be completed before transaction reservations are made.
4278 the appropriate resource reservations, locks, and fill out a ``struct
|
| /linux/Documentation/driver-api/cxl/linux/ |
| H A D | early-boot.rst | 130 /* do not allow reservations */
135 SystemRAM in `ZONE_NORMAL` during early boot, CMA reservations per-node can be
|
| /linux/fs/btrfs/ |
| H A D | block-group.h | 234 atomic_t reservations; member
|
| H A D | block-group.c | 385 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()
405 * block group's reservations counter is incremented while a read lock in btrfs_wait_block_group_reservations()
412 wait_var_event(&bg->reservations, !atomic_read(&bg->reservations)); in btrfs_wait_block_group_reservations()
1961 * to RO above, which prevents reservations from happening but in btrfs_reclaim_bgs_work()
1962 * we may have existing reservations for which allocation has in btrfs_reclaim_bgs_work()
|
| H A D | extent-tree.c | 2709 atomic_inc(&bg->reservations); in btrfs_inc_block_group_reservations()
|
| /linux/Documentation/core-api/kho/ |
| H A D | concepts.rst | 56 of that memory region may be reserved. These reservations are irrelevant for
|
| /linux/Documentation/filesystems/iomap/ |
| H A D | operations.rst | 212 such `reservations
222 This function must *only* remove delayed allocation reservations, in
312 should throw away any reservations that may have been made for the write.
317 delalloc reservations to avoid having delalloc reservations for
|
| H A D | design.rst | 357 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 D | ringbuf.rst | 179 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/Documentation/arch/powerpc/ |
| H A D | firmware-assisted-dump.rst | 320 file will change to reflect the new memory reservations.
|
| /linux/Documentation/driver-api/ |
| H A D | dma-buf.rst | 349 reservations for DMA fence workloads.
|
| /linux/mm/ |
| H A D | hugetlb.c | 156 * remain, give up any reservations based on minimum size and in unlock_or_release_subpool()
249 * Return the number of global page reservations that must be dropped.
1056 * Flags for MAP_PRIVATE reservations. These are stored in the bottom
1134 * reservations are to be un-charged from here. in resv_map_alloc()
1268 struct resv_map *reservations = vma_resv_map(vma); in clear_vma_resv_huge_pages() local
1270 if (reservations && is_vma_resv_set(vma, HPAGE_RESV_OWNER)) { in clear_vma_resv_huge_pages()
1271 resv_map_put_hugetlb_cgroup_uncharge_info(reservations); in clear_vma_resv_huge_pages()
1272 kref_put(&reservations->refs, resv_map_release); in clear_vma_resv_huge_pages()
2549 * are used by the huge page allocation routines to manage reservations.
2967 * When it's set, the allocation will bypass all vma level reservations
[all...] |
| /linux/fs/bcachefs/ |
| H A D | journal_io.c | 1799 j->reservations.cur_entry_offset < JOURNAL_ENTRY_CLOSED_VAL) { in CLOSURE_CALLBACK()
1952 * reservations that weren't fully used) and merging jset_entries that in bch2_journal_write_prep()
|
| /linux/Documentation/scheduler/ |
| H A D | sched-deadline.rst | 800 showing how SCHED_DEADLINE reservations can be created by a real-time
|
| /linux/Documentation/driver-api/usb/ |
| H A D | usb.rst | 938 With the Linux-USB stack, periodic bandwidth reservations use the
|
| /linux/Documentation/networking/dsa/ |
| H A D | dsa.rst | 507 reservations per port and per traffic class, in the ingress and egress
|