From: MRK <mrk@shiftmail.org>
To: Jeremy Sanders <jeremy@jeremysanders.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: stuck tasks
Date: Mon, 12 Apr 2010 15:38:05 +0200 [thread overview]
Message-ID: <4BC3223D.6020403@shiftmail.org> (raw)
In-Reply-To: <hpv5kt$o52$1@dough.gmane.org>
On 04/12/2010 03:02 PM, Jeremy Sanders wrote:
> It's not doing anything else on that drive. I think it would be faster but
> the option CONFIG_MULTICORE_RAID456 was switched on in this kernel, so
> there are lots of async processes fighting each other (190 of them on this
> system).
>
Oh it's this one then. I read it has already been discussed here... you
really need to remove the multicore implementation: it's experimental as
of now and *much* slower than single core. I don't know why the your
distro maintainer has activated it. What distro is that? Someone should
probably tell the maintainers to disable it by default. I think all your
problems will go away if you can recompile with multicore off.
prev parent reply other threads:[~2010-04-12 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 10:40 stuck tasks Jeremy Sanders
2010-04-12 11:06 ` MRK
2010-04-12 11:14 ` Jeremy Sanders
2010-04-12 12:49 ` MRK
2010-04-12 13:02 ` Jeremy Sanders
2010-04-12 13:38 ` MRK [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=4BC3223D.6020403@shiftmail.org \
--to=mrk@shiftmail.org \
--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 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).