Searched refs:reservations (Results 1 – 19 of 19) sorted by relevance
| /Linux-v6.1/Documentation/admin-guide/cgroup-v1/ |
| 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.
|
| /Linux-v6.1/Documentation/mm/ |
| D | hugetlbfs_reserv.rst | 64 region in the reserv_map may indicate reservations exist for the
65 range, or reservations do not exist.
70 Indicates this task is the owner of the reservations
114 was specified, then this routine returns immediately as no reservations
124 in which reservations are represented in the reservation map.
127 exists or did exist for the corresponding page. As reservations are
130 a reservation exists for the corresponding page. As reservations are
132 reservation map can also be used to determine which reservations have
137 to indicate this VMA owns the reservations.
139 The reservation map is consulted to determine how many huge page reservations
[all …]
|
| /Linux-v6.1/Documentation/filesystems/ |
| 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
|
| 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 …]
|
| /Linux-v6.1/fs/ocfs2/ |
| D | Makefile | 31 reservations.o \
|
| /Linux-v6.1/Documentation/block/ |
| D | pr.rst | 16 All implementations are expected to ensure the reservations survive
22 The following types of reservations are supported:
|
| /Linux-v6.1/Documentation/admin-guide/nfs/ |
| D | pnfs-scsi-server.rst | 21 option and the underlying SCSI device support persistent reservations.
|
| /Linux-v6.1/fs/btrfs/ |
| D | block-group.h | 190 atomic_t reservations; member
|
| D | block-group.c | 362 if (atomic_dec_and_test(&bg->reservations)) in btrfs_dec_block_group_reservations()
363 wake_up_var(&bg->reservations); in btrfs_dec_block_group_reservations()
389 wait_var_event(&bg->reservations, !atomic_read(&bg->reservations)); in btrfs_wait_block_group_reservations()
|
| D | extent-tree.c | 2631 atomic_inc(&bg->reservations); in btrfs_inc_block_group_reservations()
|
| /Linux-v6.1/Documentation/bpf/ |
| 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-v6.1/Documentation/driver-api/ |
| D | dma-buf.rst | 315 reservations for DMA fence workloads.
|
| /Linux-v6.1/Documentation/powerpc/ |
| D | firmware-assisted-dump.rst | 285 file will change to reflect the new memory reservations.
|
| /Linux-v6.1/mm/ |
| D | hugetlb.c | 1057 struct resv_map *reservations = vma_resv_map(vma); in clear_vma_resv_huge_pages() local
1059 if (reservations && is_vma_resv_set(vma, HPAGE_RESV_OWNER)) { in clear_vma_resv_huge_pages()
1060 resv_map_put_hugetlb_cgroup_uncharge_info(reservations); in clear_vma_resv_huge_pages()
1061 kref_put(&reservations->refs, resv_map_release); in clear_vma_resv_huge_pages()
|
| /Linux-v6.1/Documentation/scheduler/ |
| D | sched-deadline.rst | 769 showing how SCHED_DEADLINE reservations can be created by a real-time
|
| /Linux-v6.1/Documentation/driver-api/usb/ |
| D | usb.rst | 932 With the Linux-USB stack, periodic bandwidth reservations use the
|
| /Linux-v6.1/Documentation/x86/ |
| D | resctrl.rst | 985 end up allocating the same bits so the reservations are shared instead of
|
| /Linux-v6.1/Documentation/networking/dsa/ |
| D | dsa.rst | 503 reservations per port and per traffic class, in the ingress and egress
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | kernel-parameters.txt | 4205 use_e820 [X86] Use E820 reservations to exclude parts of
4210 no_e820 [X86] Ignore E820 reservations for PCI host
|
