From: Andi Kleen <ak@linux.intel.com>
To: "Mario 'BitKoenig' Holbe" <Mario.Holbe@TU-Ilmenau.DE>,
dm-crypt@saout.de, linux-kernel@vger.kernel.org,
Milan Broz <mbroz@redhat.com>, Alasdair G Kergon <agk@redhat.com>
Subject: Re: dm-crypt: Performance Regression 2.6.37 -> 2.6.38-rc8
Date: Thu, 10 Mar 2011 17:18:42 -0800 [thread overview]
Message-ID: <20110311011842.GA5698@alboin.amr.corp.intel.com> (raw)
In-Reply-To: <20110310175411.GB25027@darkside.kls.lan>
> Would it be possible to make CPU-affinity configurable for *single*
> kcryptd instances? Either in the way to nail a specific kcryptd to a
> specific CPU or (what would be better for me, I guess) in the way to
> completely remove CPU-affinity from a specific kcryptd, like it was
> before?
I don't think that's a good idea. You probably need to find some way
to make pcrypt (parallel crypt layer) work for dmcrypt. That may
actually give you more speedup too than your old hack because
it can balance over more cores.
Or get a system with AES-NI -- that usually solves it too.
Frankly I don't think it's a very interesting case, the majority
of workloads are not like that.
-Andi
next prev parent reply other threads:[~2011-03-11 1:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 16:45 Mario 'BitKoenig' Holbe
2011-03-08 17:35 ` [dm-crypt] " Milan Broz
2011-03-08 19:23 ` Mario 'BitKoenig' Holbe
2011-03-08 20:07 ` Milan Broz
2011-03-08 20:17 ` Mario 'BitKoenig' Holbe
2011-03-10 16:57 ` Andi Kleen
2011-03-10 17:54 ` Mario 'BitKoenig' Holbe
2011-03-11 1:18 ` Andi Kleen [this message]
2011-03-11 18:03 ` Mario 'BitKoenig' Holbe
2011-03-11 18:29 ` Milan Broz
2011-03-11 18:36 ` Andi Kleen
2011-03-12 1:05 ` Herbert Xu
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=20110311011842.GA5698@alboin.amr.corp.intel.com \
--to=ak@linux.intel.com \
--cc=Mario.Holbe@TU-Ilmenau.DE \
--cc=agk@redhat.com \
--cc=dm-crypt@saout.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbroz@redhat.com \
/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
all inboxes | Powered by JetHome®