From: Dawid Ciezarkiewicz <dpc@asn.pl>
To: David Miller <davem@davemloft.net>
Cc: stephen@dino.dnsalias.com, netdev@vger.kernel.org
Subject: Re: [RFC] Ethernet Cheap Cryptography
Date: Wed, 18 Oct 2006 11:51:46 +0200 [thread overview]
Message-ID: <200610181151.46506.dpc@asn.pl> (raw)
In-Reply-To: <20061017.202544.74747614.davem@davemloft.net>
On Wednesday, 18 October 2006 05:25, David Miller wrote:
> From: stephen@dino.dnsalias.com (Stephen J. Bevan)
> Date: Tue, 17 Oct 2006 20:21:46 -0700
>
> > * You write "frames will be delivered in order, so on the other side
> > IV can be always in sync."
>
> In fact, in addition to your comments, Linux can reorder packets
> locally within the system even within traffic for the same link.
>
> Any technology which absolutely requires in order packet delivery
> isn't going to work very well.
I've tried to put ccrypt handlers as close to hardware xmit and recv as
possible so local reorder doesn't matter. Medium doesn't reorder frames and
switches, bridges shouldn't do that neither (but as Stephen J. Bevan said
this may not be always true).
next prev parent reply other threads:[~2006-10-18 9:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 16:20 [RFC] Ethernet Cheap Cryptography Dawid Ciezarkiewicz
2006-10-15 21:35 ` James Morris
2006-10-15 22:15 ` Dawid Ciezarkiewicz
2006-10-18 3:21 ` Stephen J. Bevan
2006-10-18 3:25 ` David Miller
2006-10-18 9:51 ` Dawid Ciezarkiewicz [this message]
2006-10-18 10:16 ` David Miller
2006-10-18 11:35 ` Dawid Ciezarkiewicz
2006-10-18 9:15 ` Dawid Ciezarkiewicz
2006-10-18 14:31 ` Dawid Ciezarkiewicz
2006-10-19 3:57 ` Stephen J. Bevan
2006-10-19 15:58 ` Pawel Foremski
2006-10-20 2:18 ` Stephen J. Bevan
2006-10-20 2:59 ` David Miller
2006-10-21 2:17 ` Stephen J. Bevan
2006-10-21 2:20 ` David Miller
2006-10-20 20:18 ` Pawel Foremski
2006-10-21 1:58 ` Stephen J. Bevan
2006-10-21 2:28 ` Stephen Hemminger
2006-10-21 15:33 ` Pawel Foremski
2006-10-21 15:12 ` Pawel Foremski
2006-10-22 0:05 ` Stephen J. Bevan
2006-10-20 19:50 ` Dawid Ciezarkiewicz
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=200610181151.46506.dpc@asn.pl \
--to=dpc@asn.pl \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@dino.dnsalias.com \
/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;
as well as URLs for NNTP newsgroup(s).