On Fri, 2009-01-09 at 19:22 +1100, Dave Chinner wrote: > > > > the async code throttles at 32k outstanding. > > Yes 32K is arbitrary, but if you delete a million files fast, all > > but the first few thousand are synchronous. > > No, after the first 32k you get a mix of synchronous and async as > the async queue gets processed in parallel. This means you are > screwing up the temporal locality of the unlink of inodes. i.e. some > unlinks are being done immediately, others are being delayed until > another 32k inodes have been processed of the unlink list. > > > If we've been careful about allocation locality during untar so > that inodes that are allocated sequentially by untar will be > deleted sequential by rm -rf, then this new pattern will break those > optimisations because the unlink locality is being broken by > the some sync/some async behaviour that this queuing mechanism > creates. > You won't notice on ext34, but xfs, btrfs and probably jfs should go slower with this. The throttle should wait for one of the entries on the queue to finish, and then put this inode on the queue in order. Doing the current one synchronously will generate random IO. On XFS, create 256,000 4k files, drop caches and then time find . | xargs rm > Hmmmm - I suspect that rm -rf will also trigger lots of kernel > threads to be created. We do not want 256 kernel threads to > be spawned to bang on the serialised regions of filesystem > journals (generating lock contention) when one thread would > be sufficient.... This could be good and bad. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
