From: "David S. Miller" <davem@redhat.com>
To: rusty@rustcorp.com.au
Cc: paulus@samba.org, netdev@oss.sgi.com, fcusack@samba.org,
carlson@workingcode.com
Subject: Re: [PATCH, untested] Support for PPPOE on SMP
Date: Wed, 25 Jun 2003 20:59:41 -0700 (PDT) [thread overview]
Message-ID: <20030625.205941.41631020.davem@redhat.com> (raw)
In-Reply-To: <20030626035824.D68B62C147@lists.samba.org>
From: Rusty Russell <rusty@rustcorp.com.au>
Date: Thu, 26 Jun 2003 13:57:09 +1000
Frankly, I'm amazed anyone sees reordering in real life...
Many paths on the internet are quite reordered, this is
the first thing. In fact, I claim that any TCP stack that
doesn't do reordering detection is busted performance wise.
The second thing is that network cards can and do reorder packets.
Some PCMCIA cards do this just for fun. And ethernet _DOES NOT_
guarentee non-reordering. At a minumum, a card can use QoS values to
reorder receive of a given packet, it can also use this to reorder
transmit. Our packet schedulers do this on a software level.
If you need ordering, you need sequence numbers in your
protocol if you wish to operate over these mediums.
The case where SMP causes out-of-order packet delivery is just
academic compared to the non-local sources of reordering
mentioned above.
next prev parent reply other threads:[~2003-06-26 3:59 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-25 7:24 [PATCH, untested] Support for PPPOE on SMP Rusty Russell
2003-06-25 11:19 ` Jamal Hadi
2003-06-25 13:21 ` Michal Ostrowski
2003-06-25 13:42 ` Michal Ostrowski
2003-06-25 15:45 ` Jamal Hadi
2003-06-25 17:27 ` Michal Ostrowski
2003-06-25 22:17 ` Paul Mackerras
2003-06-25 22:56 ` Michal Ostrowski
2003-06-25 16:15 ` Stephen Hemminger
2003-06-25 16:22 ` Jamal Hadi
2003-06-25 16:39 ` Stephen Hemminger
2003-06-25 17:07 ` Jamal Hadi
2003-06-25 17:40 ` Stephen Hemminger
2003-06-25 18:00 ` Michal Ostrowski
2003-06-25 22:22 ` Paul Mackerras
2003-06-25 22:53 ` Ben Greear
2003-06-25 21:33 ` David S. Miller
2003-06-25 22:06 ` Michal Ostrowski
2003-06-26 1:04 ` David S. Miller
2003-06-26 3:57 ` Rusty Russell
2003-06-26 3:59 ` David S. Miller [this message]
2003-06-26 8:17 ` Rusty Russell
2003-06-26 8:55 ` David S. Miller
2003-06-26 10:47 ` James Carlson
2003-06-26 10:51 ` James Carlson
2003-06-26 23:18 ` Jamal Hadi
2003-06-27 11:39 ` James Carlson
2003-06-27 12:12 ` Paul Mackerras
2003-06-27 13:19 ` James Carlson
2003-06-27 14:59 ` Stephen Hemminger
2003-06-27 15:27 ` James Carlson
2003-06-28 2:21 ` Jamal Hadi
2003-06-28 22:51 ` Frank Cusack
2003-06-26 11:37 ` Michal Ostrowski
2003-06-25 16:01 ` Jason Lunz
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=20030625.205941.41631020.davem@redhat.com \
--to=davem@redhat.com \
--cc=carlson@workingcode.com \
--cc=fcusack@samba.org \
--cc=netdev@oss.sgi.com \
--cc=paulus@samba.org \
--cc=rusty@rustcorp.com.au \
/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).