Thread (16 messages) read the whole thread 16 messages, 2 authors, 2016-06-28

Re: [PATCH v6 2/8] crypto: add driver-side scomp interface

From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Date: 2016-06-24 08:37:33

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.
quoted
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help