Linux RAID subsystem development
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Eivind Sarto <eivindsarto@gmail.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [patch 1/1] raid5: speedup sync_request processing
Date: Tue, 10 Jun 2014 11:10:23 +1000	[thread overview]
Message-ID: <20140610111023.7a2e6ecd@notabene.brown> (raw)
In-Reply-To: <EC0B81A7-E03B-442F-B523-4B7154ABDC34@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]

On Mon, 9 Jun 2014 17:06:19 -0700 Eivind Sarto <eivindsarto@gmail.com> wrote:

> Ignore previous email.  Forgot to attach patch.
> 
> This is a trivial patch that improves rebuild/resync speed of raid5 arrays.
> Instead of having the resync-thread handle the stripe, it now just sets STRIPE_HANDLE and
> releases the stripe.  Allowing the resync-thread to return immediately and schedule more operations.
> 
> The speedup will increase with more drives in the array.  And it will increase further if additional
> kworker threads are enabled.  But, it improves with just the default raid5d() running.
> 
> Note: I posted this patch a while back, but nothing happened.  Not accepted, not rejected.
> 
> Trying one more time.
> 
> -eivind

I looked through my mail and found you posted much the same patch on 11th
February.
I replied as below.  You never resent (or if you did, I never got it).  You
did reply with some numbers, but that isn't the same as resubmitting the
patch with a proper description at the top.

Your new patch does mention some performance numbers in the comment so that I
a lot better.  I've applied it.

Thanks,
NeilBrown


Hi,
 thanks for the patch.
 When you include a patch as an attachment, I find it easier to work with if
 it is "text/plain" rather than "application/octet-stream".

 As your patch is justified as a performance improvement, please include
 some measurements together with a rough description of the hardware (one or
 two sentences).

 Also, the performance improvement requires that multi-threading is enabled,
 which isn't the default.  Please measure the effect of the patch when
 multi-threading not enabled.
 Maybe we should make the change you suggest be conditional on threading
 being enabled, but we can't know without numbers.

Thanks,
NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2014-06-10  1:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  0:06 [patch 1/1] raid5: speedup sync_request processing Eivind Sarto
2014-06-10  1:10 ` NeilBrown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-06-10  0:03 Eivind Sarto

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=20140610111023.7a2e6ecd@notabene.brown \
    --to=neilb@suse.de \
    --cc=eivindsarto@gmail.com \
    --cc=linux-raid@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