All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tyler Hicks <tyhicks@canonical.com>
To: Michael Schneider <michael8schneider@gmail.com>
Cc: ecryptfs@vger.kernel.org
Subject: Re: Will there be a multi CPU core version of eCryptfs?
Date: Thu, 14 Mar 2013 09:26:53 -0700	[thread overview]
Message-ID: <20130314162652.GA24036@boyd> (raw)
In-Reply-To: <loom.20130314T111312-931@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

On 2013-03-14 10:53:54, Michael Schneider wrote:
> Hello,

Hi Michael

> 
> 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% 

Drops ~70% in comparison to what?

> (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.

Possibly. Myself and others are currently looking into ways to increase
eCryptfs performance. There's an opportunity to spread out the work
across multiple cores while doing that and it is something that is being
taken into consideration.

> 
> 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 :)

You found the right place. Sit tight for a bit and maybe kernel 3.10
will have what you're wanting. Thanks for the question.

Tyler

> 
> Thanks.
> 
> Best regards,
> Michael
> 
> --
> To unsubscribe from this list: send the line "unsubscribe ecryptfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2013-03-14 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-14 10:53 Will there be a multi CPU core version of eCryptfs? Michael Schneider
2013-03-14 16:26 ` Tyler Hicks [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=20130314162652.GA24036@boyd \
    --to=tyhicks@canonical.com \
    --cc=ecryptfs@vger.kernel.org \
    --cc=michael8schneider@gmail.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 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.