From: Michael Schneider <michael8schneider@gmail.com>
To: ecryptfs@vger.kernel.org
Subject: Will there be a multi CPU core version of eCryptfs?
Date: Thu, 14 Mar 2013 10:53:54 +0000 (UTC) [thread overview]
Message-ID: <loom.20130314T111312-931@post.gmane.org> (raw)
Hello,
When using eCryptfs on a low end devices like NASs,
the CPU is often limiting the performance of reading/writing dramatically
because of the intense cryptographic workload.
I know that using cryptography on such systems is always a trade off,
but I ask myself about a possible optimization which would help very much:
On my NAS the throughput with eCryptfs drops by about 70%
(Synology DS412+, Atom D2700 - 2 Cores, Hyperthreading).
For non-encrypted operation the CPU nearly idles, when using eCryptfs
its at about 25% load. I assume that only one of the possible
four parallel CPU threads are used.
My question is "Will there be a multi CPU core version?" which would improve
performance on low powered CPUs.
I don't know, if this is the right place to ask, but it would be great
if any of the developers could give me feedback if this will be possible
in the future - crossing fingers :)
Thanks.
Best regards,
Michael
next reply other threads:[~2013-03-14 10:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 10:53 Michael Schneider [this message]
2013-03-14 16:26 ` Will there be a multi CPU core version of eCryptfs? Tyler Hicks
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=loom.20130314T111312-931@post.gmane.org \
--to=michael8schneider@gmail.com \
--cc=ecryptfs@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