Searched refs:reservations (Results 1 – 20 of 20) sorted by relevance
| /linux/Documentation/admin-guide/cgroup-v1/ |
| 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…
86 The HugeTLB controller allows to limit the HugeTLB reservations per control
119 When a HugeTLB cgroup goes offline with some reservations or faults still
126 reservations charged to it, that cgroup persists as a zombie until all HugeTLB
127 reservations are uncharged. HugeTLB reservations behave in this manner to match
129 memory is uncharged. Also, the tracking of HugeTLB reservations is a bit more
131 harder to reparent reservations at offline time.
|
| /linux/Documentation/vm/ |
| A 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
124 in which reservations are represented in the reservation map.
127 exists or did exist for the corresponding page. As reservations are
137 to indicate this VMA owns the reservations.
175 ensure reservations exist for the range 'from' - 'to'.
209 is called. This routine takes two arguments related to reservations:
317 accounting, and track any reservations associated with the subpool.
450 are decremented by the number of outstanding reservations.
[all …]
|
| /linux/Documentation/filesystems/ |
| 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
|
| A D | xfs-delayed-logging-design.rst | 538 space available in the log if we are to use static reservations, and that is
636 the amount of space available in the log for their reservations. The practical
|
| /linux/fs/ocfs2/ |
| A D | Makefile | 31 reservations.o \
|
| /linux/Documentation/block/ |
| A D | pr.rst | 16 All implementations are expected to ensure the reservations survive
22 The following types of reservations are supported:
|
| A D | biodoc.rst | 1132 8.9. VM reservations patch (Ben LaHaise)
|
| /linux/Documentation/admin-guide/nfs/ |
| A D | pnfs-scsi-server.rst | 21 option and the underlying SCSI device support persistent reservations.
|
| /linux/fs/btrfs/ |
| A D | block-group.h | 167 atomic_t reservations; member
|
| A D | block-group.c | 333 if (atomic_dec_and_test(&bg->reservations)) in btrfs_dec_block_group_reservations()
334 wake_up_var(&bg->reservations); in btrfs_dec_block_group_reservations()
360 wait_var_event(&bg->reservations, !atomic_read(&bg->reservations)); in btrfs_wait_block_group_reservations()
|
| A D | extent-tree.c | 2654 atomic_inc(&bg->reservations); in btrfs_inc_block_group_reservations()
|
| /linux/Documentation/bpf/ |
| 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/mm/ |
| A D | hugetlb.c | 1038 struct resv_map *reservations = vma_resv_map(vma); in clear_vma_resv_huge_pages() local
1040 if (reservations && is_vma_resv_set(vma, HPAGE_RESV_OWNER)) { in clear_vma_resv_huge_pages()
1041 resv_map_put_hugetlb_cgroup_uncharge_info(reservations); in clear_vma_resv_huge_pages()
1042 kref_put(&reservations->refs, resv_map_release); in clear_vma_resv_huge_pages()
|
| /linux/Documentation/powerpc/ |
| A D | firmware-assisted-dump.rst | 285 file will change to reflect the new memory reservations.
|
| /linux/Documentation/driver-api/ |
| A D | dma-buf.rst | 318 reservations for DMA fence workloads.
|
| /linux/Documentation/filesystems/caching/ |
| A D | netfs-api.rst | 611 those pages will need to have any marks and reservations removed. This can be
794 backed by a cache, -EOPNOTSUPP if the cache doesn't support reservations,
|
| /linux/Documentation/scheduler/ |
| A D | sched-deadline.rst | 769 showing how SCHED_DEADLINE reservations can be created by a real-time
|
| /linux/Documentation/networking/dsa/ |
| A D | dsa.rst | 472 reservations per port and per traffic class, in the ingress and egress
|
| /linux/Documentation/driver-api/usb/ |
| A D | usb.rst | 932 With the Linux-USB stack, periodic bandwidth reservations use the
|
| /linux/Documentation/x86/ |
| A D | resctrl.rst | 985 end up allocating the same bits so the reservations are shared instead of
|
Completed in 61 milliseconds