/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… 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 at offline time.
|
/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/fs/bcachefs/ |
H A D | journal.c | 47 return __journal_entry_is_open(j->reservations); in journal_entry_is_open() 52 union journal_res_state s = READ_ONCE(j->reservations); in bch2_journal_buf_to_text() 198 if (!journal_state_count(j->reservations, idx)) { in bch2_journal_do_writes() 245 old.v = atomic64_read(&j->reservations.counter); in __journal_entry_close() 253 } while (!atomic64_try_cmpxchg(&j->reservations.counter, in __journal_entry_close() 459 old.v = atomic64_read(&j->reservations.counter); in journal_entry_open() 473 } while (!atomic64_try_cmpxchg(&j->reservations.counter, in journal_entry_open() 506 if (__journal_entry_is_open(j->reservations)) { in journal_write_work() 691 state = READ_ONCE(j->reservations); in bch2_journal_entry_res_resize() 924 j->reservations.cur_entry_offset == JOURNAL_ENTRY_BLOCKED_VAL) { in bch2_journal_unblock() [all …]
|
H A D | journal.h | 126 return j->buf + j->reservations.idx; in journal_cur_buf() 262 }).v, &j->reservations.counter); in journal_state_buf_put() 332 old.v = atomic64_read(&j->reservations.counter); in journal_res_get_fast() 360 } while (!atomic64_try_cmpxchg(&j->reservations.counter, in journal_res_get_fast() 416 return j->reservations.cur_entry_offset == JOURNAL_ENTRY_ERROR_VAL in bch2_journal_error()
|
H A D | journal_types.h | 183 union journal_res_state reservations; member
|
H A D | journal_io.c | 1674 old.v = atomic64_read(&j->reservations.counter); in CLOSURE_CALLBACK() 1681 } while (!atomic64_try_cmpxchg(&j->reservations.counter, in CLOSURE_CALLBACK()
|
/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
|
/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/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 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/Documentation/admin-guide/nfs/ |
H A D | pnfs-scsi-server.rst | 21 option and the underlying SCSI device support persistent reservations.
|
/linux/fs/btrfs/ |
H A D | block-group.h | 232 atomic_t reservations; member
|
H A D | block-group.c | 372 if (atomic_dec_and_test(&bg->reservations)) in btrfs_dec_block_group_reservations() 373 wake_up_var(&bg->reservations); in btrfs_dec_block_group_reservations() 399 wait_var_event(&bg->reservations, !atomic_read(&bg->reservations)); in btrfs_wait_block_group_reservations()
|
H A D | extent-tree.c | 2708 atomic_inc(&bg->reservations); in btrfs_inc_block_group_reservations()
|
/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/filesystems/iomap/ |
H A D | design.rst | 344 They need to avoid waiting on transaction reservations to allow 369 For example, a write might wish to commit the reservations for the bytes
|
/linux/Documentation/driver-api/ |
H A D | dma-buf.rst | 349 reservations for DMA fence workloads.
|
/linux/Documentation/arch/powerpc/ |
H A D | firmware-assisted-dump.rst | 298 file will change to reflect the new memory reservations.
|
/linux/mm/ |
H A D | hugetlb.c | 1240 struct resv_map *reservations = vma_resv_map(vma); in clear_vma_resv_huge_pages() local 1242 if (reservations && is_vma_resv_set(vma, HPAGE_RESV_OWNER)) { in clear_vma_resv_huge_pages() 1243 resv_map_put_hugetlb_cgroup_uncharge_info(reservations); in clear_vma_resv_huge_pages() 1244 kref_put(&reservations->refs, resv_map_release); in clear_vma_resv_huge_pages()
|
/linux/Documentation/driver-api/usb/ |
H A D | usb.rst | 937 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
|
/linux/Documentation/admin-guide/ |
H A D | kernel-parameters.txt | 4702 use_e820 [X86] Use E820 reservations to exclude parts of 4707 no_e820 [X86] Ignore E820 reservations for PCI host
|