Searched refs:reservations (Results 1 – 9 of 9) sorted by relevance
99 resv_level=2 (*) Set how aggressive allocation reservations will be.100 Valid values are between 0 (reservations off) to 8101 (maximum space for reservations).102 dir_resv_level= (*) By default, directory reservations will scale with file103 reservations - users should rarely need to change this104 value. If allocation reservations are turned off, this
31 For kdump reservations, low memory is the memory area under a specific66 reservations. The user would not need to know the system memory layout75 many systems the low memory is precious and crashkernel reservations
31 reservations.o \
16 All implementations are expected to ensure the reservations survive22 The following types of reservations are supported:
244 atomic_t reservations; member
413 if (atomic_dec_and_test(&bg->reservations)) in btrfs_dec_block_group_reservations()414 wake_up_var(&bg->reservations); in btrfs_dec_block_group_reservations()440 wait_var_event(&bg->reservations, !atomic_read(&bg->reservations)); in btrfs_wait_block_group_reservations()
2803 atomic_inc(&bg->reservations); in btrfs_inc_block_group_reservations()
255 such `reservations265 This function must *only* remove delayed allocation reservations, in355 should throw away any reservations that may have been made for the write.360 delalloc reservations to avoid having delalloc reservations for
179 a strict ordering between reservations. Commits, on the other hand, are181 in the order of reservations, but only after all previous records where