public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Lachlan McIlroy <lachlan@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Donald Douwsma <donaldd@sgi.com>, xfs-oss <xfs@oss.sgi.com>, gnb@sgi.com
Subject: Re: [review] Remove the xfs refcache
Date: Tue, 18 Dec 2007 15:12:02 +1100	[thread overview]
Message-ID: <47674892.9070506@sgi.com> (raw)
In-Reply-To: <20071217071426.GA11462@infradead.org>

Christoph Hellwig wrote:
> On Mon, Dec 17, 2007 at 03:00:04PM +1100, Lachlan McIlroy wrote:
>> Hey hold on there buddy!  We may need to reactivate this code to fix some
>> performance issues.  I've acttually got this code working and proven that
>> it is one way to fix some of the NAS/NFS issues we have.
>>
>> The little comment that reads "reference cache not needed for NFS in 2.6"
>> is wrong - we do need it or something like it.
> 
> Not in XFS, though.  This thing needs to be done genericly in NFSD.
> Greg has been working on an open files cache in nfsd which should be
> helping this.
> 
> Adding a cache like this back into XFS will get my veto (at least for
> mainline where I have a bit of a say :))
> 

Greg's NFS OFC will provide better performance for strictly NFS workloads
and if all we are trying to fix here is the NFS issues then I agree with
you that the OFC should not go into XFS.

Since I have been able to reproduce some of our NAS/NFS performance problems
without NFS (that is demonstrate that the problems are in XFS) it makes some
sense to fix these in XFS.  I have observed that for some non-NFS workloads
we see a significant reduction in log traffic with the OFC in XFS so for
reasons beyond NFS there may be a need to reactivate the refcache code.  For
the moment we are still analysing the pros/cons.

  parent reply	other threads:[~2007-12-18  4:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-17  3:26 [review] Remove the xfs refcache Donald Douwsma
2007-12-17  4:00 ` Lachlan McIlroy
2007-12-17  4:12   ` Donald Douwsma
2007-12-17  5:48   ` Eric Sandeen
2007-12-17  7:15     ` Christoph Hellwig
2007-12-17  7:14   ` Christoph Hellwig
2007-12-17  7:39     ` Greg Banks
2007-12-18  4:12     ` Lachlan McIlroy [this message]
2007-12-18  7:44       ` David Chinner
2007-12-19  3:43         ` David Chinner
2008-02-07  8:35 ` Christoph Hellwig
2008-02-11 13:00   ` Donald Douwsma
2008-02-11 16:32     ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47674892.9070506@sgi.com \
    --to=lachlan@sgi.com \
    --cc=donaldd@sgi.com \
    --cc=gnb@sgi.com \
    --cc=hch@infradead.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox