linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: lilofile <lilofile@aliyun.com>, linux-raid@vger.kernel.org
Subject: Re: raid5 raid5d  multi-thread
Date: Fri, 01 Nov 2013 11:19:50 -0500	[thread overview]
Message-ID: <5273D4A6.3070308@hardwarefreak.com> (raw)
In-Reply-To: <72a920d2-2c76-41af-bcac-0dee5b36df5a@aliyun.com>

On 10/31/2013 10:27 PM, lilofile wrote:
> now in MD raid5,stripe is hande in one thread, and I found the CPU occupation is very high, why stripe is not handled in multi-thread ? is any different to implement? and what consideration in original design?

Shaohua Li has been working on a threaded RAID5 implementation for many
months now.  AFAIK it is not yet ready for inclusion nor widespread
testing by others.  See:

https://lkml.org/lkml/2013/7/30/29

-- 
Stan

      reply	other threads:[~2013-11-01 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01  3:27 raid5 raid5d multi-thread lilofile
2013-11-01 16:19 ` Stan Hoeppner [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=5273D4A6.3070308@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=lilofile@aliyun.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;
as well as URLs for NNTP newsgroup(s).