public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Dave Lloyd <dlloyd@exegy.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: [Fwd: [Fwd: xfs write speed regression 2.6.18.1 to 2.6.19.1]]
Date: Mon, 8 Jan 2007 10:33:34 +1100	[thread overview]
Message-ID: <20070107233334.GW44411608@melbourne.sgi.com> (raw)
In-Reply-To: <459ECF04.4090803@exegy.com>

On Fri, Jan 05, 2007 at 04:19:48PM -0600, Dave Lloyd wrote:
> From a co-worker. Anyone know what might have changed this between
> 2.6.18 and 2.6.19 when the issue first appeared?

IIRC< a bunch of changes went into the generic buffered I/O
path to fix deadlocks on writes if we take a page fault during
the copyin. That caused a performance regression for buffered
I/O of around that sort of figure, and the regression is slowly
being fixed up as per:

> under 2.6.20-rc3 the speeds have gone back up some, but they are 10%
> slower than 2.6.18.

So I don't think this is an XFS problem as such. Still, I will try
to do some local tests to check it out.

> and the allocations, as shown by the sequential writes (attached) are
> random.

????

> If I went all the way out to the inside tracks, you would be at about
> 490MB/Sec.
> 
> Something changed. 2.6.19 was unstable, with XFS panics on a regular basis.

Got any stack traces?

> 2.6.19.1 has not had an error yet.. (knock head on wall repeatedly).

We didn't push any changes into 2.6.19.1, so that implies bugs in
the generic code, not XFS....

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

      parent reply	other threads:[~2007-01-07 23:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 22:19 [Fwd: [Fwd: xfs write speed regression 2.6.18.1 to 2.6.19.1]] Dave Lloyd
2007-01-06 16:56 ` Eric Sandeen
2007-01-07 23:33 ` David Chinner [this message]

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=20070107233334.GW44411608@melbourne.sgi.com \
    --to=dgc@sgi.com \
    --cc=dlloyd@exegy.com \
    --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