On Tuesday April 10, [EMAIL PROTECTED] wrote: > > Seems like it would simply make more sense for the server to be allowed > to determine what the size of the cookie should be.
That is one possibility. but if the cookie gets too big, you substantially reduce the number of entries you can fit in a single reply. And if you choose to use the filename as the cookie, you end up sending the filename twice for each entry, which seems somewhat pointless. > > Of course, that doesn't help NFSv2/3/4.0. No. And while we can probably deprecate support for NFSv2 (at least in newer filesystems) I think it will be quite some years before we can think about doing the same for v3 (in fact we can probably deprecate 4.0 and 4.1 before v3 :-) So while it doesn't hurt to plan for the longer-term future, I think we need to accept that over the next 5 years, filesystems needs to cope with 64bit dir-entry cookies to be generally useful. NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
