On Wed, Apr 21, 2010 at 06:40:04PM +1000, Nick Piggin wrote: > I'm saying that dynamic registration is no good, if we don't have a > way to order the shrinkers. We can happily throw in a priority field into the shrinker structure, but at this stage in the release process I'd rather have an as simple as possible fix for the regression. And just adding the context pointer which is a no-op for all existing shrinkers fits that scheme very well. If it makes you happier I can queue up a patch to add the priorities for 2.6.35. I think figuring out any meaningful priorities will be much harder than that, though. > > If a change of interface means that we end up with shorter call > > chains, less global state, more flexibilty, better batching and IO > > patterns, less duplication of code and algorithms and it doesn't > > cause any regressions, then where's the problem? > > Yep that would all be great but I don't see how the interface change > enables any of that at all. It seems to me that the advantage goes > the other way because it doesn't put as much crap into your mount > structure and you end up with an useful traversable list of mounts as > a side-effect. There really is not need for that. The Linux VFS is designed to have superblocks independent, which actually is a good thing as global state gets in the way of scalability or just clean code. Note that a mounts list would be even worse as filesystems basically are not concerned with mount points themselves. -- 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
