netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Robert Olsson <Robert.Olsson@data.slu.se>
Cc: "'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: 2.6.7 tulip performance (with NAPI)
Date: Wed, 06 Oct 2004 14:37:11 -0700	[thread overview]
Message-ID: <41646587.7070401@candelatech.com> (raw)
In-Reply-To: <16740.17875.574967.11417@robur.slu.se>

Robert Olsson wrote:
> Ben Greear writes:
> 
>  > I tried setting the NICE level of pktgen to -10 and softirq to -18.  I
>  > still see way more packets transmitted than received.
> 
>  If you have "max_before_softirq" in your version pktgen you can try it
>  to balance your load. HZ=1000 in 2.6 can make scheduling different.

Yes, I was able to get it to smooth out by doing something like that.  I
also got better desktop performance by simply decreasing the niceness of
the pktgen thread to 0 instead of -10.

On a related note, I am now working on a way to use a hook in the
netif_wake_queue callback to wake up pktgen.  This should allow me to
have a pktgen that does not need to spin in a tight loop like it does
now.  So far, I was able to saturate two GigE ports using about 3% of
the CPU (as reported by top), using 1514 byte pkts.  Still tweaking
to fix some corner cases...

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2004-10-06 21:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 23:42 2.6.7 tulip performance (with NAPI) Ben Greear
2004-10-06 19:21 ` Robert Olsson
2004-10-06 21:37   ` Ben Greear [this message]
2004-10-07  0:56     ` Ben Greear
2004-10-07  1:08       ` David S. Miller
2004-10-07 18:09         ` Ben Greear
2004-10-11  4:07           ` David S. Miller
2004-10-07 21:11       ` Robert Olsson
2004-10-07 21:47         ` Ben Greear
2004-10-07 22:13           ` Robert Olsson
2004-10-07 23:44         ` Lennert Buytenhek
2004-10-08  9:25           ` P
2004-10-08  9:28             ` Lennert Buytenhek

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=41646587.7070401@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=Robert.Olsson@data.slu.se \
    --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).