Lines Matching refs:buffers

10 structures. Other objects - typically buffers - have their physical changes
54 keeps relogging the inode and btree buffers as they get modified in each
70 forces the log buffers holding the transactions to disk. This means that XFS is
75 log buffers made available by the log manager. By default there are 8 log
76 buffers available and the size of each is 32kB - the size can be increased up
81 buffers are full and under IO, then no more transactions can be committed until
83 be to able to issue enough transactions to keep the log buffers full and under
92 multiple times before they are committed to disk in the log buffers. If we
102 buffers. It is clear that reducing the number of stale objects written to the
111 accumulating stale objects in the log buffers.
124 metadata changes from the size and number of log buffers available. In other
163 changes to the log buffers, we need to ensure that the object we are formatting
271 committed and have formatted memory buffers attached to them. It tracks objects
283 all the items in the CIL must be written into the log via the log buffers.
331 checkpoints to be written into the log buffers in the case of log force heavy
393 Once the checkpoint is written into the log buffers, the checkpoint context is
427 written directly into the log buffers. Hence some other method of sequencing
480 ahead of time, nor how many log buffers it will take to write out, nor the
499 comparison, if we are logging full directory buffers, they are typically 4KB
500 each, so we in 1.5MB of directory buffers we'd have roughly 400 buffers and a
573 buffers. Hence items that are relogged in the log buffers will have a pin count
633 across the formatting of the objects into memory buffers (i.e. while memcpy()s
664 an ordering loop after writing all the log vectors into the log buffers but
756 		Chain log vectors and buffers together