From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, giovanni.cabiddu@gmail.com
Subject: Re: [PATCH v7 4/9] crypto: acomp - add support for lzo via scomp
Date: Tue, 20 Sep 2016 13:23:35 +0100 [thread overview]
Message-ID: <20160920122335.GA14477@SILVIXA00369791-F22-1> (raw)
In-Reply-To: <20160920092618.GA20808@gondor.apana.org.au>
Hi Herbert,
apologies for the duplicate. The previous email didn't get delivered to
the ML.
On Tue, Sep 20, 2016 at 05:26:18PM +0800, Herbert Xu wrote:
> Rather than duplicating the scratch buffer handling in every scomp
> algorithm, let's centralize this and put it into scomp.c.
Are you suggesting to hide the scratch buffers from the scomp
implementations and allocate them inside crypto_register_scomp?
Does that mean we have to go back to a scomp_alg with a flat buffer API
and linearize inside scomp?
If we take this direction, how do we support DMA from scomp
implementation? Scratch buffers are allocated using vmalloc.
Thanks,
--
Giovanni
next prev parent reply other threads:[~2016-09-20 12:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 12:49 [PATCH v7 0/9] crypto: asynchronous compression api Giovanni Cabiddu
2016-09-13 12:49 ` [PATCH v7 1/9] crypto: add " Giovanni Cabiddu
2016-09-13 12:49 ` [PATCH v7 2/9] crypto: add driver-side scomp interface Giovanni Cabiddu
2016-09-13 12:49 ` [PATCH v7 3/9] crypto: scomp - add scratch buffers allocator and deallocator Giovanni Cabiddu
2016-09-13 12:49 ` [PATCH v7 4/9] crypto: acomp - add support for lzo via scomp Giovanni Cabiddu
2016-09-20 9:26 ` Herbert Xu
2016-09-20 12:23 ` Giovanni Cabiddu [this message]
[not found] ` <20160920115140.GA12332@sivswdev01.ir.intel.com>
2016-09-22 9:22 ` Herbert Xu
2016-09-22 22:54 ` Giovanni Cabiddu
2016-09-23 15:05 ` Herbert Xu
2016-09-26 17:27 ` Giovanni Cabiddu
2016-09-27 3:07 ` Herbert Xu
2016-09-13 12:49 ` [PATCH v7 5/9] crypto: acomp - add support for lz4 " Giovanni Cabiddu
2016-09-13 12:49 ` [PATCH v7 6/9] crypto: acomp - add support for lz4hc " Giovanni Cabiddu
2016-09-13 12:49 ` [PATCH v7 7/9] crypto: acomp - add support for 842 " Giovanni Cabiddu
2016-09-13 12:49 ` [PATCH v7 8/9] crypto: acomp - add support for deflate " Giovanni Cabiddu
2016-09-13 12:49 ` [PATCH v7 9/9] crypto: acomp - update testmgr with support for acomp Giovanni Cabiddu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160920122335.GA14477@SILVIXA00369791-F22-1 \
--to=giovanni.cabiddu@intel.com \
--cc=giovanni.cabiddu@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox