netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felix Radensky <felix@allot.com>
To: hadi@cyberus.ca
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
	Ben Greear <greearb@candelatech.com>,
	netdev@oss.sgi.com
Subject: Re: Ethernet bridge performance
Date: Sun, 10 Aug 2003 10:32:43 +0300	[thread overview]
Message-ID: <3F35F51B.7080301@allot.com> (raw)
In-Reply-To: 1060284094.1024.36.camel@jzny.localdomain

[-- Attachment #1: Type: text/plain, Size: 1427 bytes --]

Hi, Jamal

I guess you were not reading my first posting
very carefully :)

2.4.22 has NAPI capable e1000 driver and I've
compiled the driver with NAPI support.

So running non-NAPI driver is not my problem.

Felix.

jamal wrote:

>Actually seems his biggest problem is he is not running
>the NAPI driver
>
>cheers,
>jamal
>
>On Thu, 2003-08-07 at 15:09, Robert Olsson wrote:
>  
>
>>Felix Radensky writes:
>> > Thanks for your help, Ben. What is skb-recycle patch
>> > and where can I find it ?
>> 
>> It's experimental and not updated for almost a year and current 
>> implementation does not add anything to SMP. Got some idea how
>> to improve this... but try to keep to slab as long as possible 
>> it has been improved.
>>
>> Routing/bridging on SMP has affinty problem. If you are passing
>> skb's say from eth0 to eth1 and they are bound on different CPU's
>> you get cache boucing since the TX-interrupts come on another CPU.
>>
>> In a recent test with pktgen:
>> 300 kpps with TX interrupts on same CPU as sender.
>> 198 kpps with TX intr on different CPU as sender.
>>
>> Recycling tries to address this but current implementation fails
>> as said.
>>
>> But you are probably hit by something else... Check were the drops 
>> happens qdisc?. NIC ring RX/TX size, Number of interrupts. ksoftird 
>> priority, link HW_FLOW control, checksumming, affinity etc. 
>>
>> 
>> Cheers.
>>						--ro
>>
>>
>>    
>>
>
>  
>


[-- Attachment #2: Type: text/html, Size: 1747 bytes --]

  parent reply	other threads:[~2003-08-10  7:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07  9:12 Ethernet bridge performance Felix Radensky
2003-08-07 15:59 ` Stephen Hemminger
2003-08-07 16:05   ` Felix Radensky
2003-08-07 16:57 ` Ben Greear
2003-08-07 17:19   ` Felix Radensky
2003-08-07 19:09     ` Robert Olsson
2003-08-07 19:21       ` jamal
2003-08-07 22:49         ` Robert Olsson
2003-08-10  7:32         ` Felix Radensky [this message]
2003-08-11  2:55           ` jamal
2003-08-11  7:52             ` Robert Olsson
     [not found]       ` <3F3601F3.6000001@allot.com>
2003-08-10 18:13         ` Ben Greear
2003-08-10 19:47           ` Andi Kleen
2003-08-10 21:49         ` Robert Olsson
2003-08-07 19:35   ` David S. Miller
2003-08-07 19:50     ` Ben Greear
2003-08-07 19:58       ` David S. Miller

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=3F35F51B.7080301@allot.com \
    --to=felix@allot.com \
    --cc=Robert.Olsson@data.slu.se \
    --cc=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).