Lines Matching full:head

228 grant head and the current log tail. That is, how much space can be
232 The first grant head is the "reserve" head. This tracks the byte count of the
239 The reserve grant head is used to accurately account for exact transaction
241 and need to write into the log. The reserve head is used to prevent new
242 transactions from taking new reservations when the head reaches the current
248 The other grant head is the "write" head. Unlike the reserve head, this grant
249 head contains an LSN and it tracks the physical space usage in the log. While
250 this might sound like it is accounting the same state as the reserve grant head
251 - and it mostly does track exactly the same location as the reserve grant head -
269 grant head does not track physical space - it only accounts for the amount of
270 reservations we currently have outstanding. Hence if the reserve head passes
274 can overcommit the reserve head without violating the physical log head and tail
279 the write head - is then reserved separately by a call to xfs_log_reserve()
281 physical log space to be reserved from the write grant head, but only if one
289 physical head of the log and so do not pin the tail of the log. If a locked item
585 reason for this limit is that to find the head and tail of the log, there must
635 	CIL Head
653 And after the flush the CIL head is empty, and the checkpoint context log