From: Herbert Xu Subject: Re: [QUESTION] multi-core, multi-crypto, ipsec/udp out of order. Date: Wed, 4 Jun 2014 08:00:49 +0800 Message-ID: <20140604000049.GA27951@gondor.apana.org.au> References: <20140602124649.GA2503@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "linux-crypto@vger.kernel.org" , "netdev@vger.kernel.org" , Steffen Klassert , "Bronstein, Dan" To: "Hsieh, Che-Min" Return-path: Received: from helcar.apana.org.au ([209.40.204.226]:48632 "EHLO helcar.apana.org.au" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754074AbaFDAA5 (ORCPT ); Tue, 3 Jun 2014 20:00:57 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: 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 Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt