On Tue, Sep 22, 2015 at 10:39:53AM -0400, Dan Streetman wrote: > > hmm, that's true, and that would simplify the code a lot! No need for > the header anymore. But, since the sw driver is sooo much slower, it > would be important to be able to communicate the alignment and size > limits to the caller of the crypto compression api, via cra_alignmask > and cra_blocksize (for minimum size), as well as new fields for max > size (maybe cra_maxsize) and buffer length multiple - i.e. the buffer > length must be a multiple of N (maybe cra_blockmult or cra_blockmodulo > or something). Otherwise callers would get unexpectedly slow > performance if they use the wrong alignment or size. Right. So who actually uses this? Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
