public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: packet re-ordering on SMP machines.
Date: Sun, 25 Aug 2002 00:18:20 -0700	[thread overview]
Message-ID: <3D6884BC.5090004@candelatech.com> (raw)

It appears from my initial tests on 2.4.20-pre4, that packets sent on
one port, and received on another port on the same machine (via a cross-over
cable), can be re-ordered.  I see about 2000 reordered packets per 5,000,000 packets
sent (sending about 70,000 packets-per-second on a dual-port e1000 NIC.)

By re-ordered, I mean that a method called from process_backlog in dev.c
is being handed packets in a different order than they are being poked into
the driver with hard_start_xmit on the other interface.  If each CPU can be running the
process_backlog, then I can see how this could be happening.


1)  Is this expected behaviour?

2)  Is there any standard (ie configurable) way to enforce strict ordering on an
     SMP system?

3)  If answer to 2 is no, would you all be interested in a patch that
     did allow strict ordering (if indeed I can figure out how to write one)?

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>       <Ben_Greear AT excite.com>
President of Candela Technologies Inc      http://www.candelatech.com
ScryMUD:  http://scry.wanfear.com     http://scry.wanfear.com/~greear



             reply	other threads:[~2002-08-25  7:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25  7:18 Ben Greear [this message]
2002-08-25  7:07 ` packet re-ordering on SMP machines David S. Miller
2002-08-25 14:41 ` Alan Cox
2002-08-25 17:00   ` Ben Greear
2002-08-25 20:44     ` Alan Cox
2002-08-25 22:49   ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2002-08-25  8:01 Manfred Spraul
2002-08-25 15:56 jamal

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=3D6884BC.5090004@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    /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