netdev - Re: [QUESTION] multi-core, multi-crypto, ipsec/udp out of order.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140604000049.GA27951@gondor.apana.org.au>
Date:	Wed, 4 Jun 2014 08:00:49 +0800
From:	Herbert Xu <herbert@...dor.apana.org.au>
To:	"Hsieh, Che-Min" <cheminh@....qualcomm.com>
Cc:	"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Steffen Klassert <steffen.klassert@...unet.com>,
	"Bronstein, Dan" <dbronste@....qualcomm.com>
Subject: Re: [QUESTION] multi-core, multi-crypto,  ipsec/udp out of order.

On Tue, Jun 03, 2014 at 01:48:56PM +0000, Hsieh, Che-Min wrote:
> Herbert:
> Sorry, what is "in-tree" driver? This is Qcom crypto driver. It is part of android linux 3-10. I think Stanimir Varbanov is working on upstreaming the crypto driver. The driver version he cuts off, does static crypto engine assignment, i.e. crypto HW is assigned to a TFM on  cra_init. That scheme is simple. But, under the same TFM, it does not take advantage of multiple crypto HW working in parallel. Later, we put in dynamic engine assignment per request, as described in the previous mail thread.

An in-tree driver is one that's in the mainline kernel.

Cheers,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html