Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1412877
| From | Herbert Xu <herbert@gondor.apana.org.au> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag |
| Date | 2016-06-03 10:00 +0200 |
| Message-ID | <rFSbn-od-3@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <rDnY6-2JR-15@gated-at.bofh.it> <rFwaR-3wC-13@gated-at.bofh.it> <rFR5D-8aL-9@gated-at.bofh.it> <rFRfj-8ef-7@gated-at.bofh.it> <rFRyF-9r-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Jun 03, 2016 at 03:10:31PM +0800, Baolin Wang wrote: > On 3 June 2016 at 14:51, Herbert Xu <herbert@gondor.apana.org.au> wrote: > > On Fri, Jun 03, 2016 at 02:48:34PM +0800, Baolin Wang wrote: > >> > >> If we move the IV generation into the crypto API, we also can not > >> handle every algorithm with the bulk interface. Cause we also need to > >> use different methods to map one whole bio or map one sector according > >> to the algorithm whether can support bulk mode or not. Please correct > >> me if I misunderstand your points. Thanks. > > > > Which ones can't be handled this way? > > What I mean is bulk mode and sector mode's difference is not only the > IV handling method, but also the method to map the data with > scatterlists. > Then we have two processes in dm-crypt ( crypt_convert_block() and > crypt_convert_bulk_block() ) to handle the data, so we can not handle > every algorithm with the bulk interface. As I asked, which algorithm can't you handle through the bulk interface, assuming it did all the requisite magic to generate the correct IV? Cheers, -- Email: Herbert Xu <herbert@gondor.apana.org.au> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag Herbert Xu <herbert@gondor.apana.org.au> - 2016-06-02 10:30 +0200
Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag Baolin Wang <baolin.wang@linaro.org> - 2016-06-03 08:50 +0200
Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag Herbert Xu <herbert@gondor.apana.org.au> - 2016-06-03 09:00 +0200
Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag Baolin Wang <baolin.wang@linaro.org> - 2016-06-03 09:20 +0200
Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag Herbert Xu <herbert@gondor.apana.org.au> - 2016-06-03 10:00 +0200
Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag Baolin Wang <baolin.wang@linaro.org> - 2016-06-03 10:20 +0200
Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag Herbert Xu <herbert@gondor.apana.org.au> - 2016-06-03 10:30 +0200
Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag Baolin Wang <baolin.wang@linaro.org> - 2016-06-03 11:30 +0200
Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag Herbert Xu <herbert@gondor.apana.org.au> - 2016-06-03 12:20 +0200
Re: [RFC v2 2/3] crypto: Introduce CRYPTO_ALG_BULK flag Baolin Wang <baolin.wang@linaro.org> - 2016-06-03 12:50 +0200
csiph-web