From: Andi Kleen <andi@firstfloor.org>
To: Christian Schmidt <schmidt@digadd.de>
Cc: dm-crypt@saout.de, linux-kernel@vger.kernel.org
Subject: Re: [dm-crypt] kworkers for dm-crypt locked to CPU core 0?
Date: Mon, 25 Mar 2013 03:32:11 -0700 [thread overview]
Message-ID: <m2obe7ixck.fsf@firstfloor.org> (raw)
In-Reply-To: <51501C0A.5060406@digadd.de> (Christian Schmidt's message of "Mon, 25 Mar 2013 10:42:34 +0100")
Christian Schmidt <schmidt@digadd.de> writes:
>
> Is there a way I can make the scheduler put those on multiple cores?
Submit the IO from multiple cores. Don't use dd.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
WARNING: multiple messages have this Message-ID (diff)
From: Andi Kleen <andi@firstfloor.org>
To: Christian Schmidt <schmidt@digadd.de>
Cc: dm-crypt@saout.de, linux-kernel@vger.kernel.org
Subject: Re: kworkers for dm-crypt locked to CPU core 0?
Date: Mon, 25 Mar 2013 03:32:11 -0700 [thread overview]
Message-ID: <m2obe7ixck.fsf@firstfloor.org> (raw)
In-Reply-To: <51501C0A.5060406@digadd.de> (Christian Schmidt's message of "Mon, 25 Mar 2013 10:42:34 +0100")
Christian Schmidt <schmidt@digadd.de> writes:
>
> Is there a way I can make the scheduler put those on multiple cores?
Submit the IO from multiple cores. Don't use dd.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2013-03-25 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 9:42 [dm-crypt] kworkers for dm-crypt locked to CPU core 0? Christian Schmidt
2013-03-25 9:42 ` Christian Schmidt
2013-03-25 10:32 ` Andi Kleen [this message]
2013-03-25 10:32 ` Andi Kleen
2013-03-25 10:55 ` [dm-crypt] " Christian Schmidt
2013-03-25 10:55 ` Christian Schmidt
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=m2obe7ixck.fsf@firstfloor.org \
--to=andi@firstfloor.org \
--cc=dm-crypt@saout.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schmidt@digadd.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 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.