From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH v6 2/8] crypto: add driver-side scomp interface
Date: Fri, 24 Jun 2016 09:37:28 +0100 [thread overview]
Message-ID: <20160624083728.GA15549@sivswdev01.ir.intel.com> (raw)
In-Reply-To: <20160623105034.GA10475@gondor.apana.org.au>
On Thu, Jun 23, 2016 at 06:50:34PM +0800, Herbert Xu wrote:
> No that's not the problem. The problem is that you can't kmalloc
> 64K of memory. kmalloc requires physically contiguous memory and
> you cannot rely on having 64K of contiguous memory.
It is clear now. Thanks.
> > > This totally breaks down once you go to DMA, where an SG list is
> > > required.
> > scomp backends should be used only for software implementations.
> > A driver backend which needs DMA should plug into acomp.
>
> What I'm saying is that the current strategy of using vmalloc
> memory as input/output buffers cannot possibly work with acomp
> since you cannot do DMA over vmalloc memory.
I'll remove scomp and refit the software algos to plug into acomp
directly.
Would it be admissible if software algos implementations will vmalloc
the source and the destination buffers for linearizing the scatter gather
lists and will operate on those?
Thanks,
--
Giovanni
next prev parent reply other threads:[~2016-06-24 8:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 8:16 [PATCH v6 0/8] crypto: asynchronous compression api Giovanni Cabiddu
2016-06-08 8:16 ` [PATCH v6 1/8] crypto: add " Giovanni Cabiddu
2016-06-08 8:16 ` [PATCH v6 2/8] crypto: add driver-side scomp interface Giovanni Cabiddu
2016-06-13 8:56 ` Herbert Xu
2016-06-22 15:53 ` Giovanni Cabiddu
2016-06-23 10:50 ` Herbert Xu
2016-06-24 8:37 ` Giovanni Cabiddu [this message]
2016-06-24 9:26 ` Herbert Xu
2016-06-28 7:41 ` Giovanni Cabiddu
2016-06-28 7:51 ` Herbert Xu
2016-06-08 8:16 ` [PATCH v6 3/8] crypto: acomp - add support for lzo via scomp Giovanni Cabiddu
2016-06-08 8:16 ` [PATCH v6 4/8] crypto: acomp - add support for lz4 " Giovanni Cabiddu
2016-06-08 8:16 ` [PATCH v6 5/8] crypto: acomp - add support for lz4hc " Giovanni Cabiddu
2016-06-08 8:16 ` [PATCH v6 6/8] crypto: acomp - add support for 842 " Giovanni Cabiddu
2016-06-08 8:16 ` [PATCH v6 7/8] crypto: acomp - add support for deflate " Giovanni Cabiddu
2016-06-08 8:16 ` [PATCH v6 8/8] 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=20160624083728.GA15549@sivswdev01.ir.intel.com \
--to=giovanni.cabiddu@intel.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