From: Tyler Hicks <tyhicks@canonical.com>
To: Kenneth Waegeman <Kenneth.Waegeman@UGent.be>
Cc: ecryptfs@vger.kernel.org
Subject: Re: hardware acceleration
Date: Tue, 23 Sep 2014 10:45:10 -0500 [thread overview]
Message-ID: <20140923154509.GA7673@boyd> (raw)
In-Reply-To: <20140923161329.Horde.JgatAND6UQ5UIYAJzVa0rtA@webmail.ugent.be>
[-- Attachment #1: Type: text/plain, Size: 1464 bytes --]
On 2014-09-23 16:13:29, Kenneth Waegeman wrote:
> Hi,
>
> I've read that ecryptfs supports hardware acceleration, but I don't find how
> to enable this or check if it is working.
This is all handled by the kernel crypto API. Users (you) and kernel
crypto API consumers (eCryptfs) are not expected to do anything to
enable hardware acceleration. The crypto API makes the decision of
whether your hardware supports acceleration and if it should be used.
I don't know of an easy way to check if it is enabled. What I would
suggest doing would be:
1) Set up your eCryptfs mount
- This will result in eCryptfs autoloading the crypto drivers
2) Look at /proc/crypto
- Look at all entries with the name "cbc(aes)"
- Now compare the "priority" fields for each of those entries
- If the highest priority entry's driver field is "cbc-aes-aesni",
eCryptfs should be using the AES-NI driver
> How can I find out which cyphers are supported, and how can I see if it
> actually uses the hardware acceleration?
Loaded crypto modules are described in /proc/crypto. You'll need to load
any kernel crypto modules that are not loaded before they're described
in /proc/crypto.
Tyler
>
> Thanks again!!
>
> Kenneth
>
> --
> 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: 819 bytes --]
prev parent reply other threads:[~2014-09-23 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 14:13 hardware acceleration Kenneth Waegeman
2014-09-23 15:45 ` 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=20140923154509.GA7673@boyd \
--to=tyhicks@canonical.com \
--cc=Kenneth.Waegeman@UGent.be \
--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;
as well as URLs for NNTP newsgroup(s).