On Wed, 2010-02-03 at 19:06 -0500, Chuck Lever wrote: > My only concern would be that we perhaps should not assume that every > 2.6 NFS client does this. There was an awful lot of churn at one point > as you were getting all of these ducks in a row. Before you changed the > underlying RPC transports to return only ENOTCONN, for instance, was > this behavior the same? I wouldn't swear to it in the 2.6.7 - .9 > vintage kernels. Every change in this area is performance sensitive, and should certainly be tested carefully; particularly so with older kernels. However we shouldn't forget that the changes to the client were motivated by poor performance against a variety of servers, in a variety of workloads and so it isn't unreasonable to expect that SUSE, Red Hat, Debian, Oracle, etc do have an interest in fixing their NFS clients. My question would rather therefore be: do they already have a fix in their latest kernel revisions, and if not, are they able to give us a timeframe? Cheers Trond -- 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
