xfs
[Top] [All Lists]

Re: TAKE - reintroduce the nfs inode reference cache

To: Andi Kleen <ak@xxxxxxx>
Subject: Re: TAKE - reintroduce the nfs inode reference cache
From: Steve Lord <lord@xxxxxxx>
Date: Tue, 06 Mar 2001 14:56:50 -0600
Cc: Steve Lord <lord@xxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: Message from Andi Kleen <ak@xxxxxxx> of "Tue, 06 Mar 2001 21:43:22 +0100." <20010306214322.A14781@xxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
> On Tue, Mar 06, 2001 at 02:24:43PM -0600, Steve Lord wrote:
> > 
> > OK, I am probably talking rubbish with this code, if someone feels like try
> ing
> > it out please do and let me know if it helps. I thought I was seeing 
> > improvements, but thinking about the code, and trying the tests again I
> > am not seeing improvements.
> 
> If XFS is doing the truncate on linux inode count zeroing (in i_ops->release)
> then it should only happen when the file is expunged from the dcache, which
> can be never and should not happen after every NFS RPC unless the machine
> is trashing heavily. 
> 
> 
> -Andi


This is f_ops release, not iops, the normal case is from close. A quick
mod to the code to not do the release in this case but delay it until later
appears to help. Ananth is going to test it on his 100Mbit network and we
will see if this helps. However, should the f_ops release code be the culprit
we may be able to find a simpler way to fix this.

Steve



<Prev in Thread] Current Thread [Next in Thread>