From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: johnpol@2ka.mipt.ru
Cc: linux-kernel@vger.kernel.org, Michal Ludvig <michal@logix.cz>,
Fruhwirth Clemens <clemens@endorphin.org>,
Andrew Morton <akpm@osdl.org>, James Morris <jmorris@redhat.com>,
cryptoapi@lists.logix.cz, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 1/2] CryptoAPI: prepare for processing multiple buffers at a time
Date: Sat, 15 Jan 2005 01:41:30 +0300 [thread overview]
Message-ID: <20050115014130.2dcd3f2e@zanzibar.2ka.mipt.ru> (raw)
In-Reply-To: <20050115013103.05698f1a@zanzibar.2ka.mipt.ru>
On Sat, 15 Jan 2005 01:31:03 +0300
Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
>
> Crypto routing.
> This feature allows the same session to be processed by several devices/algorithms.
> For example if you need to encrypt data and then sign it in TPM device you can create
> one route to encryption device and then route it to TPM device. (Note: this feature
> must be discussed since there is no time slice after session allocation, only in
> crypto_device->data_ready() method and there are locking issues in ->callback() method).
Actually it is already impleneted by
crypto_session_alloc();
route manipulations
crypto_session_add();
And sessions can be (re)routed inside crypto devices itself.
Evgeniy Polyakov
Only failure makes us experts. -- Theo de Raadt
next prev parent reply other threads:[~2005-01-14 22:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 22:31 Fw: " Evgeniy Polyakov
2005-01-14 22:31 ` Evgeniy Polyakov
2005-01-14 22:32 ` Evgeniy Polyakov
2005-01-14 22:33 ` Evgeniy Polyakov
2005-01-14 22:34 ` Evgeniy Polyakov
2005-01-14 22:41 ` Evgeniy Polyakov [this message]
[not found] <Xine.LNX.4.44.0411301009560.11945-100000@thoron.boston.redhat.com>
[not found] ` <Pine.LNX.4.61.0411301722270.4409@maxipes.logix.cz>
[not found] ` <20041130222442.7b0f4f67.davem@davemloft.net>
2005-01-11 17:03 ` PadLock processing multiple blocks " Michal Ludvig
2005-01-11 17:08 ` [PATCH 1/2] " Michal Ludvig
2005-01-14 13:10 ` [PATCH 1/2] CryptoAPI: prepare for processing multiple buffers " Michal Ludvig
2005-01-14 14:20 ` Fruhwirth Clemens
2005-01-14 16:40 ` Michal Ludvig
2005-01-15 12:45 ` Fruhwirth Clemens
2005-01-18 16:49 ` James Morris
2005-01-20 3:30 ` David McCullough
2005-01-20 13:47 ` James Morris
2005-03-03 10:50 ` David McCullough
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050115014130.2dcd3f2e@zanzibar.2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=akpm@osdl.org \
--cc=clemens@endorphin.org \
--cc=cryptoapi@lists.logix.cz \
--cc=davem@davemloft.net \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal@logix.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®