public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jakob Oestergaard <jakob@unthought.net>,
	linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: NFS+SMP+XFS problems, Take II
Date: Wed, 6 Oct 2004 14:26:10 +0100	[thread overview]
Message-ID: <20041006142610.A30867@infradead.org> (raw)
In-Reply-To: <20041006125931.GU18307@unthought.net>; from jakob@unthought.net on Wed, Oct 06, 2004 at 02:59:31PM +0200

On Wed, Oct 06, 2004 at 02:59:31PM +0200, Jakob Oestergaard wrote:
> 
> Dear all,
> 
> The dcache patch (originally from Neil Brown, adapted for 2.6.8.1 by me)
> has been included in the current 2.6.9 RC. It *seemed* that this patch
> solved the XFS+NFS+SMP problem completely, and that it would then be
> possible to finally run an NFS server with XFS on an SMP machine.
> 
> Well, close, but not close enough.

As I told in the thread it's not enough.  I checked in two more XFS fixes,
they're all in 2.6.9-rc3.


  reply	other threads:[~2004-10-06 13:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06 12:59 NFS+SMP+XFS problems, Take II Jakob Oestergaard
2004-10-06 13:26 ` Christoph Hellwig [this message]
2004-10-06 13:48   ` Jakob Oestergaard

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=20041006142610.A30867@infradead.org \
    --to=hch@infradead.org \
    --cc=jakob@unthought.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-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