Re: [PATCH 22/24] xfs: rework xfs_iflush_cluster() dirty inode iteration

Christoph Hellwig
2020-05-24T05:33:00Z

On Sun, May 24, 2020 at 09:23:19AM +1000, Dave Chinner wrote:
> That's the exact opposite way the follow-on patchset I have goes.
> xfs_inode_item_push() goes away entirely because tracking 30+ inodes
> in the AIL for a single writeback IO event is amazingly inefficient
> and consumes huge amounts of CPU unnecessarily.

Ok. It might still make sense to move the checks and locking into
xfs_iflush, as the code flow is much easier to follow that way.