public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [Gelato-technical] Serious performance degradation on a RAID withkernel 2.6.11
Date: Wed, 06 Apr 2005 21:50:13 +0000	[thread overview]
Message-ID: <200504062150.j36LoEg31463@unix-os.sc.intel.com> (raw)
In-Reply-To: <16978.62532.841151.100745@napali.hpl.hp.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 1006 bytes --]

Andreas Hirstius wrote on Wednesday, April 06, 2005 1:33 AM
> The problems mentioned in this discussion about the Fusion-MPT I can
> perfectly reproduce on my boxes with 2.6.11, but only with pages sizes
> 4k and 8k;
> With 16k and 64k pages I don't see any problem at all !!!
> Actually I see block size <-> page size correlations which are similiar
> to the correlations I see in my setup...
> i.e. 2.6.11 and 4k pages:
>     dd ...bs@96: 40MB/s
>     dd ...bs92: 74MB/s
>
> i.e. 2.6.11 and 8k pages:
>     dd ...bs92: 56MB/s
>     dd ...bs\x16384: 74MB/s

It is very odd.  I think it has something to do with generic file read
ahead logic.  The read ahead window did not push far enough to keep the
disk busy.  Some of the size calculation are in unit of page, so smaller
page size will have smaller effective read ahead size.  Try look into
mm/readahead.c.  I bet you can find the answer to your performance problem
there.  If not, then I guess we have to keep on looking ;-)




      parent reply	other threads:[~2005-04-06 21:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-05 20:25 [Gelato-technical] Serious performance degradation on a RAID with David Mosberger
2005-04-05 20:43 ` [Gelato-technical] Serious performance degradation on a RAID Rob Fowler
2005-04-06  2:13 ` [Gelato-technical] Serious performance degradation on a RAID with kernel 2.6.11 Duraid Madina
2005-04-06  4:45 ` [Gelato-technical] Serious performance degradation on a RAID with David Mosberger
2005-04-06  4:53 ` [Gelato-technical] Serious performance degradation on a RAID with kernel 2.6.11 Duraid Madina
2005-04-06  5:10 ` David Mosberger
2005-04-06  5:56 ` [Gelato-technical] Serious performance degradation on a RAID withkernel 2.6.11 Chen, Kenneth W
2005-04-06  7:29 ` [Gelato-technical] Serious performance degradation on a RAID Andreas Hirstius
2005-04-06  7:30 ` Andreas Hirstius
2005-04-06  7:32 ` David Mosberger
2005-04-06  7:34 ` Andreas Hirstius
2005-04-06  8:33 ` Andreas Hirstius
2005-04-06 16:58 ` David Mosberger
2005-04-06 18:57 ` Andreas Hirstius
2005-04-06 21:50 ` Chen, Kenneth W [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=200504062150.j36LoEg31463@unix-os.sc.intel.com \
    --to=kenneth.w.chen@intel.com \
    --cc=linux-ia64@vger.kernel.org \
    /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