From: Tyler Hicks <tyhicks@canonical.com>
To: "Stefan Dröge" <stefan@sdroege.de>
Cc: ecryptfs@vger.kernel.org
Subject: Re: ecryptfs with aes-ni slower bug
Date: Wed, 15 Feb 2012 04:48:16 -0600 [thread overview]
Message-ID: <20120215104815.GB1991@boyd> (raw)
In-Reply-To: <CAB89gJErehp2bw6XuWghBXT9D4632rgtowUVqSsna2ng8XQ5Sw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 680 bytes --]
On 2012-02-15 11:43:21, Stefan Dröge wrote:
> Hi all,
> A while ago I read at phoronix, that ecryptfs is actually slower when
> having loaded the aesni-intel kernel module.
> Out of curiosiy I checked whether this problem still exists in the
> Ubuntu 12.04 alpha2, and it does.
> I tried to find infos to this in the mailing list archive, but I found nothing.
>
> So my question: Is somebody working on this?
No, not currently. I've been focusing on stability rather than
performance.
I'd love for someone else to become interested in the problem and dig
in. Otherwise, it will have to wait a while longer until I get some free
cycles to look into it.
Tyler
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-02-15 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-15 10:43 ecryptfs with aes-ni slower bug Stefan Dröge
2012-02-15 10:48 ` Tyler Hicks [this message]
2012-02-15 16:16 ` Dustin Kirkland
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=20120215104815.GB1991@boyd \
--to=tyhicks@canonical.com \
--cc=ecryptfs@vger.kernel.org \
--cc=stefan@sdroege.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox