From: John Robinson <john.robinson@anonymous.org.uk>
To: Tao Guo <glorioustao@gmail.com>
Cc: Jeremy Sanders <jeremy@jeremysanders.net>, linux-raid@vger.kernel.org
Subject: Re: async/X threads and rebuild slowdown
Date: Tue, 16 Mar 2010 13:49:42 +0000 [thread overview]
Message-ID: <4B9F8C76.9010702@anonymous.org.uk> (raw)
In-Reply-To: <318b7ac71003160624m16aad423lddca62c31021b104@mail.gmail.com>
On 16/03/2010 13:24, Tao Guo wrote:
> I also meet this problem in several of my machines. If I change back
> to kernel 2.6.18, it is
> OK, but in 2.6.32 kernel, the performance is really poor.
>
> At last I found a solution, set CONFIG_MULTICORE_RAID456=n when
> compiling raid456 module,
> then everything goes normal. My machines do have multicore cpu, so it
> is weird :<
> Maybe there is something wrong with the CONFIG_MULTICORE_RAID456 enabled code?
I remember it being discussed on this list, so yes I think there is or was.
Cheers,
John.
next prev parent reply other threads:[~2010-03-16 13:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 12:41 async/X threads and rebuild slowdown Jeremy Sanders
2010-03-16 13:24 ` Tao Guo
2010-03-16 13:49 ` John Robinson [this message]
2010-03-23 21:08 ` Dan Williams
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=4B9F8C76.9010702@anonymous.org.uk \
--to=john.robinson@anonymous.org.uk \
--cc=glorioustao@gmail.com \
--cc=jeremy@jeremysanders.net \
--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 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.