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.
83  * given cui log item. We use only 1 iovec, and we point that
84  * at the cui_log_format structure embedded in the cui item.
86  * slots in the cui item have been filled.
108  * The unpin operation is the last place an CUI is manipulated in the log. It is
110  * either case, the CUI transaction has been successfully committed to make it
111  * this far. Therefore, we expect whoever committed the CUI to either construct
113  * drop the log's CUI reference now that the log is done with it.
126  * The CUI has been either committed or aborted if the transaction has been
128  * constructed and thus we free the CUI here directly.
138  * Allocate and initialize an cui item with the given number of extents.
208  * the transaction is cancelled, drop our reference to the CUI and free the
356 /* Add this deferred CUI to the transaction. */
439 /* Is this recovered CUI ok? */
509 	 * CUI.  If any are bad, then assume that all are bad and  in xfs_refcount_recover_work()
510 	 * just toss the CUI.  in xfs_refcount_recover_work()
693  * item from the cui format structure which was logged on disk.
694  * It allocates an in-core cui, copies the extents from the format
695  * structure into it, and adds the cui to the AIL with the given
796  * transaction in the log. Its purpose is to cancel the corresponding CUI if it
797  * was still in the log. To do this it searches the AIL for the CUI with an id
799  * reference, which removes the CUI from the AIL and frees it.