hardware acceleration

hardware acceleration

[Kenneth Waegeman]

Hi,

I've read that ecryptfs supports hardware acceleration, but I don't  
find how to enable this or check if it is working.
How can I find out which cyphers are supported, and how can I see if  
it actually uses the hardware acceleration?

Thanks again!!

Kenneth

Re: hardware acceleration

[Tyler Hicks]

[-- 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 --]

Hardware acceleration

[louis]

[-- Attachment #1.1: Type: text/plain, Size: 671 bytes --]

Dear team,


I’m trying to make Wireguard use CPU’s hardware crypto engine . The hardware crypto engine can be driven by linux kernel. And it has registered the algorithms which it supports to the linux kernel as I can see those by “cat /proc/crypto”. Unfortunately , there’s no CHACHA available. Is there any good suggestions about how I can make Wireguard use the engine?
Such as change the crypto suite to “GCM-AES”? Or other greater?


Hope to hear you.
Regards.


Louis Michael  Networking Architect
Tel.: +86 185 0008 4208
E-Mail:louis@ukl-1.com
Web site:www.ukl-1.com
Address:Room 50629, 6F,Building D, Galaxy SOHO, Dongcheng District, Beijing, China

[-- Attachment #1.2: Type: text/html, Size: 2664 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard