On Wed, Jan 14, 2009 at 03:01:51PM +0800, Huang Ying wrote:
>
> Current cryptd works well for AES-NI implementation. But how about
> somebody want cryptd(cbc(aes)), and don't care about the driver.
That's not an issue, if the user wants then all he has to do is
create cryptd(cbc(aes)) (how that i
On Wed, 2009-01-14 at 14:53 +0800, Herbert Xu wrote:
> On Wed, Jan 14, 2009 at 02:44:08PM +0800, Huang Ying wrote:
> > Because:
> >
> > 1. if use %s, you can only request cryptd(), not
> >cryptd(), because generated new algorithm instance has
> >algorithm name: and driver name cryptd().
>
On Wed, Jan 14, 2009 at 02:44:08PM +0800, Huang Ying wrote:
> Because:
>
> 1. if use %s, you can only request cryptd(), not
>cryptd(), because generated new algorithm instance has
>algorithm name: and driver name cryptd().
This is intentional. For the purposes we talked about we should
Because:
1. if use %s, you can only request cryptd(), not
cryptd(), because generated new algorithm instance has
algorithm name: and driver name cryptd().
2. Generated cryptd-ed algorithm will have the same algorithm name and
higher priority, but some user may not want to use cryptd-ed
