[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060929094809.GA31117@2ka.mipt.ru>
Date: Fri, 29 Sep 2006 13:48:09 +0400
From: Evgeniy Polyakov <johnpol@....mipt.ru>
To: Andreas Jellinghaus <aj@...hirelabs.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org
Subject: Re: [ACRYPTO] New asynchronous crypto layer (acrypto) release.
On Thu, Sep 28, 2006 at 03:23:43PM +0200, Andreas Jellinghaus (aj@...hirelabs.com) wrote:
> Evgeniy Polyakov wrote:
> >Hello.
> >
> >I'm pleased to announce asynchronous crypto layer (acrypto) [1] release
> >for 2.6.18 kernel tree. Acrypto allows to handle crypto requests
> >asynchronously in hardware.
> >
> >Combined patchset includes:
> > * acrypto core
> > * IPsec ESP4 port to acrypto
> > * dm-crypt port to acrypto
>
> so I should be able to replace a plain 2.6.18 kernel with one
> with this patchset and use dm-crypt'ed partitions (e.g. swap,
> encrypted root filesystem) as usual without further changes?
>
> Did anyone test this with success?
>
> Regards, Andreas
As I answered in your first e-mail, yes, you just need to patch 2.6.18
tree and load one of the crypto provider.
Acrypto works with request/response model, i.e. you ask acrypto core to
perform some operation on given buffers and if it can, it will call
your callback when it is ready (or some error happend and acrypto was
unable to reroute request to other device), otherwise it will return error.
With such a model it is possible to extend acrypto to any kind of
operations on buffers, not only crypto related, for example it is
possible to onload IPsec header transformation, perform DMA between
specified areas and much more.
--
Evgeniy Polyakov
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists