On Thu, Feb 26, 2015 at 2:00 PM, Chuck Lever <chuck.lever@xxxxxxxxxx> wrote: >> The alternative would be to add a "barrier" operation to allow the >> setattr code to wait for all RPC calls before ours to complete (it >> would have to wait not just for READ, but also GETATTR and all other >> operations to the file). We could do that too. > > Yes. A barrier is usually heavyweight, though. And I thought there > was some exclusion between GETATTR and SETATTR, so forcing an > inode revalidation should work too? Or would that result in an > unneeded data cache invalidation? > I found a better solution, I think. Please see the 5 patches I just sent out. -- Trond Myklebust Linux NFS client maintainer, PrimaryData trond.myklebust@xxxxxxxxxxxxxxx -- 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
