On Mon, 2008-07-21 at 04:10 -0400, Christoph Hellwig wrote: > On Sun, Jul 20, 2008 at 09:43:50AM -0700, David Woodhouse wrote: > > The way GFS1 (and also XFS iirc) handles it is to build up a complete > > list of responses to readdir() in a buffer, drop the lock, and then > > iterate over that buffer calling filldir(). I don't much like that > > version either. > > Yes. My prefered mid-term solution would to simply lift that code from > XFS (where it's nicely isolated and all code is prefixed with hack_) to > nfsd so that local users don't aren't penalized for this. > Reiserfs also uses the local buffer and lock dropping trick, and that's what I would do for now in btrfs. But, the extent allocation tree also needs recursive locking, so I'm going to take a stab at that as soon as I get the pending patch list merged. -chris -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
