On Wed, Mar 02, 2011 at 09:12:20AM -0500, Christoph Hellwig wrote: > On Wed, Mar 02, 2011 at 02:06:02PM +1100, Dave Chinner wrote: > > I'm open to ideas here - I could convert the bdi flusher > > infrastructure to cmwqs rather than using worker threads, or move > > all dirty inode tracking and writeback into XFS, or ??? > > Tejun posted patches to convert the writeback threads to workqueues. > But I think sooner or later we should stop using VFS dirty state for > metadata. By allowing the dirty_inode operation to return a value > and say it shouldn't be marked dirty that could be done relatively > easily. Yeah, it doesn't seem like there's an easy way around that. I guess I'll start by tracking VFS dirty inodes via a tag in the per-ag radix tree and kick writeback via a new xfssynd work operation. I'll see if that is sufficient to avoid the OOM problem without needing to log the inodes in the .dirty_inode callback or changing it's prototype. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
