Lines Matching full:cui

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