All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: Jon Nelson <jnelson-linux-raid@jamponi.net>
Cc: Neil Brown <neilb@suse.de>, Linux-Raid <linux-raid@vger.kernel.org>
Subject: Re: Awful Raid10,f2 performance
Date: Tue, 16 Dec 2008 23:01:47 +0100	[thread overview]
Message-ID: <20081216220147.GA22148@rap.rap.dk> (raw)
In-Reply-To: <cccedfc60812160753w609e50efga655d34a9e0b4bce@mail.gmail.com>

On Tue, Dec 16, 2008 at 09:53:39AM -0600, Jon Nelson wrote:
> On Tue, Dec 16, 2008 at 9:26 AM, Jon Nelson
> <jnelson-linux-raid@jamponi.net> wrote:
> > On Tue, Dec 16, 2008 at 4:10 AM, Keld Jørn Simonsen <keld@dkuug.dk> wrote:
> >> On Mon, Dec 15, 2008 at 10:28:30PM -0600, Jon Nelson wrote:
> >>> On Mon, Dec 15, 2008 at 10:03 PM, Keld Jørn Simonsen <keld@dkuug.dk> wrote:
> >>>
> >>> > there was a pach to speed up raid10,f2 check in a recent kernel,
> >>> > something like 2.6.27. It did improve thruput from something
> >>> > like 40 % to about 90 %. What kernel are you using?
> >>>
> >>> 2.6.25.18-0.2-default
> >>
> >> I believe the patch arrived in a later kernel. If you can try it out
> >> with a vanilla kernel and report, I think it would be quite interesting.
> >
> > I'm pretty sure I did try it out and did have an improvement.
> > However, thanks to the power of the openSUSE build service, I am going
> > to build a kernel just now, if I can.
> 
> Scratch that. I decided to just do this at home. The suse kernel
> 2.6.25.18-0.2 appears to have this patch already. Thus, I've been
> running with this patch.

OK, well, then the patch did not apply to check, but only to resync.
One could write up a similar patch for check as what was done for
resync. The idea of the previous patch was to read quite much data in a
striped way, say 10 - 20 MB at a time.

best regards
keld
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-12-16 22:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 14:11 Awful Raid10,f2 performance Jon Nelson
2008-06-02 14:53 ` Tomasz Chmielewski
2008-06-02 15:09   ` Jon Nelson
2008-06-02 18:30     ` Keld Jørn Simonsen
2008-12-15 13:33     ` Jon Nelson
2008-12-15 21:38       ` Neil Brown
2008-12-16  2:47         ` Jon Nelson
2008-12-16  4:03           ` Keld Jørn Simonsen
2008-12-16  4:28             ` Jon Nelson
2008-12-16 10:10               ` Keld Jørn Simonsen
2008-12-16 15:26                 ` Jon Nelson
2008-12-16 15:53                   ` Jon Nelson
2008-12-16 22:01                     ` Keld Jørn Simonsen [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=20081216220147.GA22148@rap.rap.dk \
    --to=keld@dkuug.dk \
    --cc=jnelson-linux-raid@jamponi.net \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.