Lines Matching refs:reclaim
138 * Select the next per-ag structure to iterate during the walk. The reclaim
220 /* avoid new or reclaimable inodes. Leave for reclaim code to flush */
225 /* If we can't grab the inode, it must on it's way to reclaim. */
427 * reclaim of inodes to catch any that the above delwri flush skipped.
533 * Every sync period we need to unpin all items, reclaim inodes and sync
637 /* propagate the reclaim tag up into the perag radix tree */
678 /* clear the reclaim tag from the perag radix tree */
703 * lists the inode states and the reclaim actions necessary for non-blocking
704 * reclaim:
709 * bad - reclaim
710 * shutdown EIO unpin and reclaim
711 * clean, unpinned 0 reclaim
712 * stale, unpinned 0 reclaim
717 * dirty, sync flush 0 reclaim
723 * sufficient to correctly decide the reclaim action here. The checks in
737 * trying to reclaim them to minimise the amount of time spent waiting. For
741 * bad => reclaim
742 * shutdown => unpin and reclaim
745 * stale => reclaim
746 * clean => reclaim
748 * dirty, sync => flush, wait and reclaim
760 * with us starting reclaim on the inode. Once we have the
766 /* ignore as it is already under reclaim */
783 goto reclaim;
786 goto reclaim;
796 goto reclaim;
798 goto reclaim;
804 goto reclaim;
810 * call into reclaim to find it in a clean state instead of waiting for
812 * then the next reclaim pass will flush the inode, and if the error
813 * is permanent then the next sync reclaim will reclaim the inode and
818 "inode 0x%llx background reclaim flush failed with %d",
825 * We could return EAGAIN here to make reclaim rescan the inode tree in
828 * state. Instead, return 0 to let the next scheduled background reclaim
829 * attempt to reclaim the inode again.
833 reclaim: