On Tue, Oct 04, 2011 at 05:52:38PM +0200, Benny Halevy wrote: > OK, I'm going to use the common hash table also for the layout state > which will have to use the same encoding linage. > > It's a non-trivial rewrite of the layout state mechanisms but I > it seems to simplify the code overall and will be more efficient > in terms of lookup complexity (hash table vs. linear list) Note later patches change the stateid lookup a little further, to per-client lookup based on the "idr" code. (I'm not actually sure what idr uses underneath--looks like some kind of radix tree from a quick check.) I think the changes should all work for layout stateid's too, but let me know if you run into any problems. > I'm pretty hosed right now but I'd like to finish this > before the Bakeathon so we can test the result there. Great, thanks for keeping that code alive. I won't be able to make the bakeathon but please bug me and I'll make a special effort to be responsive to bugs reported from the bakeathon as I know you'll have limited testing time.... --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
