Thread (55 messages) 55 messages, 8 authors, 2004-12-14

Re: Asynchronous crypto layer.

From: Eugene Surovegin <hidden>
Date: 2004-10-30 20:56:31

On Sun, Oct 31, 2004 at 01:04:15AM +0400, Evgeniy Polyakov wrote:
On Sat, 30 Oct 2004 13:35:50 -0700
Eugene Surovegin [off-list ref] wrote:
quoted
On Fri, Oct 29, 2004 at 06:06:52PM +0400, Evgeniy Polyakov wrote:
quoted
If we have a hardware accelerator chip, than we _already_ have improvements 
with even the worst async crypto layer, since software and hardware 
will work in parrallel.
This is not true. 

For example, if chip request setup and PCI transfer takes more than 
just using sw implementation. This is reality for AES and short 
packets.
You have dataflow of packets, if invoce expenses take less time
then you will win.
Yes, but as I said for short packets, AES and fast box for example 
this might not be true.
More than 1kbyte of data to be encrypted already beats time
need for software encryption on 266 mhz.
OK, what about 64 byte packets? I'm not saying hw crypto is useless, 
what I'm saying is it's not that obvious that having hw crypto will 
help in _all_ situations.
And what about asynchronous crypto? 
Asynchronous? Never heard of it. Did you mean asymmetric?

If yes, ok, I _think_ hw crypto will help, provided we have kernel API 
for such stuff.

--
Eugene
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help