Lines Matching full:cui

47  * Freeing the CUI requires that we remove it from the AIL if it has already
48  * been placed there. However, the CUI may not yet have been placed in the AIL
51  * count to ensure only the last caller frees the CUI.
80  * given cui log item. We use only 1 iovec, and we point that
81  * at the cui_log_format structure embedded in the cui item.
83  * slots in the cui item have been filled.
104  * The unpin operation is the last place an CUI is manipulated in the log. It is
106  * either case, the CUI transaction has been successfully committed to make it
107  * this far. Therefore, we expect whoever committed the CUI to either construct
109  * drop the log's CUI reference now that the log is done with it.
122  * The CUI has been either committed or aborted if the transaction has been
124  * constructed and thus we free the CUI here directly.
134  * Allocate and initialize an cui item with the given number of extents.
200  * the transaction is cancelled, drop our reference to the CUI and free the
250  * update succeeds or fails to support the CUI/CUD lifecycle rules.
267 	 * 1.) releases the CUI and frees the CUD  in xfs_trans_log_finish_refcount_update()
446 /* Is this recovered CUI ok? */
494 	 * CUI.  If any are bad, then assume that all are bad and  in xfs_cui_item_recover()
495 	 * just toss the CUI.  in xfs_cui_item_recover()
666  * item from the cui format structure which was logged on disk.
667  * It allocates an in-core cui, copies the extents from the format
668  * structure into it, and adds the cui to the AIL with the given
714  * transaction in the log. Its purpose is to cancel the corresponding CUI if it
715  * was still in the log. To do this it searches the AIL for the CUI with an id
717  * reference, which removes the CUI from the AIL and frees it.