Re: [1/many] acrypto: Kconfig

[Evgeniy Polyakov]

On Mon, 07 Mar 2005 15:33:06 -0800
"Randy.Dunlap" <rddunlap@xxxxxxxx> wrote:

> Evgeniy Polyakov wrote:
> > diff -Nru /tmp/empty/Kconfig ./acrypto/Kconfig
> > --- /tmp/empty/Kconfig	1970-01-01 03:00:00.000000000 +0300
> > +++ ./acrypto/Kconfig	2005-03-07 21:21:33.000000000 +0300
> > @@ -0,0 +1,30 @@
> > +menu "Asynchronous crypto layer"
> > +
> > +config ACRYPTO
> > +	tristate "Asynchronous crypto layer"
> > +	select CONNECTOR
> > +	--- help ---
> > +	It supports:
> > +	 - multiple asynchronous crypto device queues
> > +	 - crypto session routing
> > +	 - crypto session binding
> > +	 - modular load balancing
> > +	 - crypto session batching genetically implemented by design
> Just curious, what genetics?

:)
All other stacks requires special flags and various complex schemas 
to support batching,
but acrypto provides session queue to the low-level driver, 
so it does not require any special cruft to support session batching.
So we have batching just after new driver birth, 
that is why it is genetic.

> > +	 - crypto session priority
> > +	 - different kinds of crypto operation(RNG, asymmetrical crypto, HMAC and any other
>                                       operation (RNG, ... )
> > +
> > +config SIMPLE_LB
> > +	tristate "Simple load balancer"
> > +	depends on ACRYPTO
> > +	--- help ---
> > +	Simple load balancer returns device with the lowest load
> > +	(device has the least number of session in it's queue) if it exists.
>                                          sessions in its
> > +
> > +config ASYNC_PROVIDER
> > +	tristate "Asynchronous crypto provider (AES CBC)"
> > +	depends on ACRYPTO && (CRYPTO_AES || CRYPTO_AES_586)
> > +	--- help ---
> > +	Asynchronous crypto provider based on synchronous crypto layer.
> > +	It supports AES CBC crypto mode (may be changed by source edition).
> > +
> > +endmenu

Thank you for your comments, I will put updates into the queue,
and push them if acrypto will be commited.

> -- 
> ~Randy


	Evgeniy Polyakov

Only failure makes us experts. -- Theo de Raadt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/