Lines Matching full:rui

50  * Freeing the RUI requires that we remove it from the AIL if it has already
51  * been placed there. However, the RUI may not yet have been placed in the AIL
54  * count to ensure only the last caller frees the RUI.
87  * given rui log item. We use only 1 iovec, and we point that
88  * at the rui_log_format structure embedded in the rui item.
90  * slots in the rui item have been filled.
113  * The unpin operation is the last place an RUI is manipulated in the log. It is
115  * either case, the RUI transaction has been successfully committed to make it
116  * this far. Therefore, we expect whoever committed the RUI to either construct
118  * drop the log's RUI reference now that the log is done with it.
131  * The RUI has been either committed or aborted if the transaction has been
133  * constructed and thus we free the RUI here directly.
143  * Allocate and initialize an rui item with the given number of extents.
219  * the transaction is cancelled, drop our reference to the RUI and free the
391 /* Add this deferred RUI to the transaction. */
468 /* Is this recovered RUI ok? */
584 	 * RUI.  If any are bad, then assume that all are bad and  in xfs_rmap_recover_work()
585 	 * just toss the RUI.  in xfs_rmap_recover_work()
732  * item from the rui format structure which was logged on disk.
733  * It allocates an in-core rui, copies the extents from the format
734  * structure into it, and adds the rui to the AIL with the given
835  * transaction in the log. Its purpose is to cancel the corresponding RUI if it
836  * was still in the log. To do this it searches the AIL for the RUI with an id
838  * reference, which removes the RUI from the AIL and frees it.