| /openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | hugetlb.rst | 24 …ugepagesize>.rsvd.limit_in_bytes # set/show limit of "hugepagesize" hugetlb reservations
25 …ize>.rsvd.max_usage_in_bytes # show max "hugepagesize" hugetlb reservations and no-reserve …
26 …hugetlb.<hugepagesize>.rsvd.usage_in_bytes # show current reservations and no-reserve f…
90 The HugeTLB controller allows to limit the HugeTLB reservations per control
123 When a HugeTLB cgroup goes offline with some reservations or faults still
130 reservations charged to it, that cgroup persists as a zombie until all HugeTLB
131 reservations are uncharged. HugeTLB reservations behave in this manner to match
133 memory is uncharged. Also, the tracking of HugeTLB reservations is a bit more
135 harder to reparent reservations at offline time.
|
| /openbmc/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 …]
|
| /openbmc/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 | 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 currently held by active transactions. It is a purely in-memory
240 reservations amounts and the exact byte count that modifications actually make
[all …]
|
| H A D | xfs-online-fsck-design.rst | 1659 This reduces the worst case size of transaction reservations by breaking the
2457 reservations pin the tail of the ondisk log.
2542 clean up the space reservations that were made for the new btree, and reap the
2553 b. For unclaimed portions of incore reservations, create a regular deferred
2801 The space reservations used to create the new metadata can be used here if
3072 which are key to enabling resource reservations for active transactions.
4275 completed before transaction reservations are made.
4278 the appropriate resource reservations, locks, and fill out a ``struct
|
| /openbmc/qemu/docs/system/ |
| H A D | pr-manager.rst | 5 SCSI persistent reservations allow restricting access to block devices
15 implementation of persistent reservations to a separate object,
31 so that QEMU will not be able to effect persistent reservations
60 Multipath devices and persistent reservations
|
| /openbmc/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
|
| /openbmc/linux/fs/ocfs2/ |
| H A D | Makefile | 31 reservations.o \
|
| /openbmc/u-boot/doc/ |
| H A D | README.bcm7xxx | 99 * accommodate stblinux bmem/CMA reservations.
130 * reservations.
|
| /openbmc/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:
|
| /openbmc/linux/Documentation/admin-guide/nfs/ |
| H A D | pnfs-scsi-server.rst | 21 option and the underlying SCSI device support persistent reservations.
|
| /openbmc/qemu/docs/tools/ |
| H A D | qemu-pr-helper.rst | 15 SCSI persistent reservations allow restricting access to block devices
|
| /openbmc/linux/fs/btrfs/ |
| H A D | block-group.h | 217 atomic_t reservations; member
|
| H A D | block-group.c | 374 if (atomic_dec_and_test(&bg->reservations)) in btrfs_dec_block_group_reservations()
375 wake_up_var(&bg->reservations); in btrfs_dec_block_group_reservations()
401 wait_var_event(&bg->reservations, !atomic_read(&bg->reservations)); in btrfs_wait_block_group_reservations()
|
| /openbmc/qemu/docs/interop/ |
| H A D | pr-helper.rst | 8 can delegate implementation of persistent reservations to an external
|
| /openbmc/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
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | dma-buf.rst | 333 reservations for DMA fence workloads.
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | firmware-assisted-dump.rst | 285 file will change to reflect the new memory reservations.
|
| /openbmc/linux/mm/ |
| H A D | hugetlb.c | 120 * remain, give up any reservations based on minimum size and in unlock_or_release_subpool()
213 * Return the number of global page reservations that must be dropped.
1032 * Flags for MAP_PRIVATE reservations. These are stored in the bottom
1110 * reservations are to be un-charged from here. in resv_map_alloc()
1244 struct resv_map *reservations = vma_resv_map(vma); in clear_vma_resv_huge_pages() local
1246 if (reservations && is_vma_resv_set(vma, HPAGE_RESV_OWNER)) { in clear_vma_resv_huge_pages()
1247 resv_map_put_hugetlb_cgroup_uncharge_info(reservations); in clear_vma_resv_huge_pages()
1248 kref_put(&reservations->refs, resv_map_release); in clear_vma_resv_huge_pages()
1409 * have no page reserves. This check ensures that reservations are in dequeue_hugetlb_folio_vma()
2689 * are used by the huge page allocation routines to manage reservations
[all...] |
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | CAL-1.0-Combined-Work-Exception | 317 any further reservations, conditions, or other provisions on any
|
| H A D | CAL-1.0 | 317 any further reservations, conditions, or other provisions on any
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp-kernel.md | 729 Broadcast messages are particularly onerous for tag reservations. When a message
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-deadline.rst | 772 showing how SCHED_DEADLINE reservations can be created by a real-time
|
| /openbmc/linux/Documentation/driver-api/usb/ |
| H A D | usb.rst | 937 With the Linux-USB stack, periodic bandwidth reservations use the
|
| /openbmc/linux/Documentation/arch/x86/ |
| H A D | resctrl.rst | 1135 end up allocating the same bits so the reservations are shared instead of
|