[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160418084155.GA18513@gondor.apana.org.au>
Date: Mon, 18 Apr 2016 16:41:56 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Baolin Wang <baolin.wang@...aro.org>
Cc: David Miller <davem@...emloft.net>,
Alasdair G Kergon <agk@...hat.com>,
Mike Snitzer <snitzer@...hat.com>, Jens Axboe <axboe@...com>,
dm-devel@...hat.com, Andrew Morton <akpm@...ux-foundation.org>,
david.s.gordon@...el.com, Tom Lendacky <thomas.lendacky@....com>,
Robert Jarzmik <robert.jarzmik@...e.fr>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
smueller@...onox.de, tadeusz.struk@...el.com,
Masanari Iida <standby24x7@...il.com>, shli@...nel.org,
Mark Brown <broonie@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Arnd Bergmann <arnd@...db.de>,
LKML <linux-kernel@...r.kernel.org>,
linux-crypto@...r.kernel.org, linux-raid@...r.kernel.org
Subject: Re: [PATCH v2 0/4] Introduce bulk mode for crypto engine framework
On Mon, Apr 18, 2016 at 04:40:36PM +0800, Baolin Wang wrote:
>
> Simply to say, now there are many different hardware engines for
> different vendors, some engines can support bulk block but some can
> not (or no cipher hardware engine), then the dm-crypt can not know
> your hardware engine features. If the dm-crypt send one bulk block to
> low level, but the engine driver can not support bulk block, then it
> will crash. So we did the merging action in driver level not dm-crypt
> level.
Surely we can handle it in the crypto API layer, just as we do GSO
in the network stack for drivers that can't handle TSO?
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
Powered by blists - more mailing lists