Re: [PATCH] crypto: aesni-intel - avoid IPsec re-ordering

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Jan 20, 2016 at 12:31:46AM -0800, Raj Ammanur wrote:
> 
> RAJ: ok. would it also be useful to be able to set the length as a module
> load time parameter?

That would be a bad interface.  If we wanted to have an adjustable
limit it needs to be set by the entity that is creating the tfm,
i.e., IPsec.
 
> RAJ: hmm, thats true, yes.
> 
> so, is the below description, that you wrote in one of your email replies,
> the solution for which you are going to create a patch?
> 
> > So what I'm thinking of is to have the softirq path forcibly regain
> > control from cryptd where possible.  This is tricky because cryptd
> > might be in the middle of processing a request.  So that's why I'd
> > like to disable softirqs while we're processing a request.

Yes.

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



[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux