netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: jamal <hadi@cyberus.ca>
Cc: netdev@oss.sgi.com
Subject: Re: packet re-ordering on SMP machines.
Date: Sun, 25 Aug 2002 21:34:47 -0700	[thread overview]
Message-ID: <3D69AFE7.6020902@candelatech.com> (raw)
In-Reply-To: Pine.GSO.4.30.0208252046250.675-100000@shell.cyberus.ca


jamal wrote:

> That doesnt sound impressive at all. I know it's about .8 of wire rate
> but you should be able to exceed that.
> Robert was generating in the range of 800Kpps with that NIC if i recall
> corectly

I had only tested 1514 byte pkts, so I was getting around 880Mbps,
which is pretty good as far as I know.

I see about 255 kpps when sending 64 byte pkts to myself.  Still
dropping about 1 in 4000 packets at this speed.  I think most of Robert's
tests didn't involve actually doing something with the received packet
though, and I am inspecting it for latency, sequence number, etc.

I'm even doing a __get_timeofday() call to calculate the latency...need
to find a faster way to do that...

If I only allocate/scan 1 per 100 packets (ie alloc one packet and send it 100 times),
then I get a more respectable 365kpps.  Robert's patch should definately help!

> Also if you have SMP, tie each onto a CPU.

That's with the irq_afinity thing in proc, right?

> Additionaly get the skb recycler patch from Robert, it should improve
> things even more.

Do you happen to have a URL for this?

Actually, the various network tweaks are relatively hard to find
(at least to find the most up-to-date coppies).  It would be great if
there was a place where they were all concentrated.

> 
> 
>>Also, I see the hard_start_xmit call failing 5876 times out of 2719493
>>calls (for example).  The code that calls the method looks like this:
>>
> 
> 
> I dont have access to that NIC. But a stoopid question: Have you tried
> increasing the transmit queue via ifconfig? 1000 packets is reasonable
> for gige.

I upped it, but it didn't stop the errors.  The NIC is still performing,
so it may not be a real problem...

Thanks for the info,
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-26  4:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.GSO.4.30.0208251149320.29461-100000@shell.cyberus.ca>
2002-08-25 18:32 ` packet re-ordering on SMP machines Ben Greear
2002-08-26  0:52   ` jamal
2002-08-26  4:34     ` Ben Greear [this message]
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
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=3D69AFE7.6020902@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.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).