All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: packet re-ordering on SMP machines.
Date: Sun, 25 Aug 2002 10:00:00 -0700	[thread overview]
Message-ID: <3D690D10.5040601@candelatech.com> (raw)
In-Reply-To: 1030286473.16651.7.camel@irongate.swansea.linux.org.uk

Alan Cox wrote:
> On Sun, 2002-08-25 at 08:18, Ben Greear wrote:
> 
>>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?
> 
> Yes
> 
> 
>>2)  Is there any standard (ie configurable) way to enforce strict ordering on an
>>     SMP system?
> 
> No
> 
> 
>>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)?
> 
> 
> You should never need it. Ethernet, hubs, switches, routers, internet
> backbones etc will all cause packet re-ordering. You should also expect
> the percentage of re-ordered frames on the net to rise and rise. 

I would like to detect the number of pkts that such backbone hardware does
re-order, so if my end machine is also re-ordering, I cannot get valid
numbers.

Thanks,
Ben

> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


-- 
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 16:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25  7:18 packet re-ordering on SMP machines Ben Greear
2002-08-25  7:07 ` David S. Miller
2002-08-25 14:41 ` Alan Cox
2002-08-25 17:00   ` Ben Greear [this message]
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
2002-08-25 15:56 jamal
2002-08-25 18:32 ` Ben Greear
2002-08-26  0:52   ` jamal
2002-08-26  4:34     ` Ben Greear
2002-08-26 11:20       ` jamal
2002-08-26 23:03       ` Xiaoliang (David) Wei
2002-08-26 23:20         ` Ben Greear
2002-08-27 10:59         ` jamal
2002-08-27 11:12           ` Andi Kleen
2002-08-27 12:05             ` jamal
2002-08-27 12:20               ` Andi Kleen
2002-08-27 13:06                 ` kuznet
2002-08-27 13:13                   ` Andi Kleen
2002-08-27 13:24                     ` kuznet
2002-09-15  8:42                     ` Harald Welte
2002-09-15 21:55                       ` Alexey Kuznetsov
2002-08-27 17:22                 ` Cheng Jin
2002-08-27 17:33                   ` Andi Kleen
2002-08-27 19:43               ` Xiaoliang (David) Wei

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=3D690D10.5040601@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.