Lines Matching refs:reservations
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
242 transactions from taking new reservations when the head reaches the current
243 tail. It will block new reservations in a FIFO queue and as the log tail moves
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
270 reservations we currently have outstanding. Hence if the reserve head passes
271 over the tail of the log all it means is that new reservations will be throttled
273 to remove the overcommit and start taking new reservations. In other words, we
284 Code using permanent reservations must always log the items they hold
821 space available in the log if we are to use static reservations, and that is
919 the amount of space available in the log for their reservations. The practical