linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Keld Jørn Simonsen" <keld@dkuug.dk>
To: linux-raid@vger.kernel.org
Cc: NeilBrown <neilb@suse.de>
Subject: [PATCH md] Speed up raid10 resync, especially for 'far' layout
Date: Tue, 5 Aug 2008 12:14:30 +0200	[thread overview]
Message-ID: <20080805101429.GA16040@rap.rap.dk> (raw)

Speed up raid10 resync, especially for 'far' layout

This patch speeds up resync for raid10, especially for the 'far' 
layout, where reading is done in 32 MiB increments and the moving of
heads is therefore much reduced compared to the previous 2 MiB size,
nd the 'far' property of striping read can be employed.

A speed up of more than 50 % has been reported.

Signed-off-by: Keld Simonsen <keld@dkuug.dk>

### Diffstat output:
 raid10.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff -u linux-2.6.25.10/drivers/md/raid10.c linux-2.6.25.10-ks/drivers/md/raid10.c
--- linux-2.6.25.10/drivers/md/raid10.c	2008-07-03 05:46:47.000000000 +0200
+++ linux-2.6.25.10-ks/drivers/md/raid10.c	2008-07-12 18:28:59.438235317 +0200
@@ -80,7 +80,7 @@
 //#define RESYNC_BLOCK_SIZE PAGE_SIZE
 #define RESYNC_SECTORS (RESYNC_BLOCK_SIZE >> 9)
 #define RESYNC_PAGES ((RESYNC_BLOCK_SIZE + PAGE_SIZE-1) / PAGE_SIZE)
-#define RESYNC_WINDOW (2048*1024)
+#define RESYNC_WINDOW (2048*1024*16)
 
 /*
  * When performing a resync, we need to read and compare, so
@@ -686,7 +686,7 @@
  *    there is no normal IO happeing.  It must arrange to call
  *    lower_barrier when the particular background IO completes.
  */
-#define RESYNC_DEPTH 32
+#define RESYNC_DEPTH 32*16
 
 static void raise_barrier(conf_t *conf, int force)
 {

             reply	other threads:[~2008-08-05 10:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 10:14 Keld Jørn Simonsen [this message]
2008-08-05 11:53 ` [PATCH md] Speed up raid10 resync, especially for 'far' layout Jon Nelson
2008-08-05 13:22   ` Keld Jørn Simonsen
2008-08-05 13:25     ` Jon Nelson

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=20080805101429.GA16040@rap.rap.dk \
    --to=keld@dkuug.dk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).