Home
last modified time | relevance | path

Searched refs:reservations (Results 1 – 25 of 27) sorted by relevance

12

/linux-6.15/Documentation/admin-guide/cgroup-v1/
H A Dhugetlb.rst24 …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-6.15/Documentation/mm/
H A Dhugetlbfs_reserv.rst62 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
122 in which reservations are represented in the reservation map.
125 exists or did exist for the corresponding page. As reservations are
135 to indicate this VMA owns the reservations.
173 ensure reservations exist for the range 'from' - 'to'.
207 is called. This routine takes two arguments related to reservations:
316 accounting, and track any reservations associated with the subpool.
449 are decremented by the number of outstanding reservations.
[all …]
/linux-6.15/Documentation/filesystems/
H A Docfs2.rst99 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-6.15/fs/bcachefs/
H A Djournal.h145 ~JOURNAL_STATE_BUF_MASK) + j->reservations.idx; in journal_cur_buf()
275 }).v, &j->reservations.counter); in journal_state_buf_put()
347 old.v = atomic64_read(&j->reservations.counter); in journal_res_get_fast()
377 } while (!atomic64_try_cmpxchg(&j->reservations.counter, in journal_res_get_fast()
434 return j->reservations.cur_entry_offset == JOURNAL_ENTRY_ERROR_VAL in bch2_journal_error()
H A Djournal.c40 return __journal_entry_is_open(j->reservations); in journal_entry_is_open()
45 union journal_res_state s = READ_ONCE(j->reservations); in bch2_journal_buf_to_text()
250 old.v = atomic64_read(&j->reservations.counter); in __journal_entry_close()
493 old.v = atomic64_read(&j->reservations.counter); in journal_entry_open()
540 if (__journal_entry_is_open(j->reservations)) { in journal_write_work()
775 state = READ_ONCE(j->reservations); in bch2_journal_entry_res_resize()
1011 old.v = atomic64_read(&j->reservations.counter); in bch2_journal_unblock()
1027 old.v = atomic64_read(&j->reservations.counter); in __bch2_journal_block()
1484 j->reservations.idx = journal_cur_seq(j); in bch2_fs_journal_start()
1609 atomic64_set(&j->reservations.counter, in bch2_fs_journal_init()
[all …]
H A Djournal_types.h169 union journal_res_state reservations; member
H A Djournal_io.c1725 j->reservations.cur_entry_offset < JOURNAL_ENTRY_CLOSED_VAL) { in CLOSURE_CALLBACK()
/linux-6.15/Documentation/arch/arm64/
H A Dkdump.rst31 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-6.15/fs/ocfs2/
H A DMakefile31 reservations.o \
/linux-6.15/Documentation/block/
H A Dpr.rst16 All implementations are expected to ensure the reservations survive
22 The following types of reservations are supported:
/linux-6.15/Documentation/admin-guide/nfs/
H A Dpnfs-scsi-server.rst21 option and the underlying SCSI device support persistent reservations.
/linux-6.15/Documentation/filesystems/xfs/
H A Dxfs-delayed-logging-design.rst16 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
166 of the btree. As such, the reservations are quite complex because we have to
233 reservations currently held by active transactions. It is a purely in-memory
242 transactions from taking new reservations when the head reaches the current
256 count" reaches zero and the initial set of unit reservations have been
262 enough free space in the log to fulfill all of the pending reservations and
[all …]
H A Dxfs-online-fsck-design.rst1659 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-6.15/fs/btrfs/
H A Dblock-group.h232 atomic_t reservations; member
H A Dblock-group.c372 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()
/linux-6.15/Documentation/filesystems/iomap/
H A Doperations.rst210 such `reservations
220 This function must *only* remove delayed allocation reservations, in
321 The function should throw away any reservations that may have been
327 delalloc reservations to avoid having delalloc reservations for
H A Ddesign.rst348 They need to avoid waiting on transaction reservations to allow
378 For example, a write might wish to commit the reservations for the bytes
/linux-6.15/Documentation/bpf/
H A Dringbuf.rst179 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-6.15/Documentation/arch/powerpc/
H A Dfirmware-assisted-dump.rst320 file will change to reflect the new memory reservations.
/linux-6.15/Documentation/driver-api/
H A Ddma-buf.rst349 reservations for DMA fence workloads.
/linux-6.15/mm/
H A Dhugetlb.c1271 struct resv_map *reservations = vma_resv_map(vma); in clear_vma_resv_huge_pages() local
1273 if (reservations && is_vma_resv_set(vma, HPAGE_RESV_OWNER)) { in clear_vma_resv_huge_pages()
1274 resv_map_put_hugetlb_cgroup_uncharge_info(reservations); in clear_vma_resv_huge_pages()
1275 kref_put(&reservations->refs, resv_map_release); in clear_vma_resv_huge_pages()
/linux-6.15/Documentation/scheduler/
H A Dsched-deadline.rst771 showing how SCHED_DEADLINE reservations can be created by a real-time
/linux-6.15/Documentation/driver-api/usb/
H A Dusb.rst937 With the Linux-USB stack, periodic bandwidth reservations use the
/linux-6.15/Documentation/arch/x86/
H A Dresctrl.rst1204 end up allocating the same bits so the reservations are shared instead of
/linux-6.15/Documentation/networking/dsa/
H A Ddsa.rst507 reservations per port and per traffic class, in the ingress and egress

12