From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Simon Kirby <sim@netnation.com>
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
"David S. Miller" <davem@redhat.com>,
ralph+d@istop.com, hadi@shell.cyberus.ca, xerox@foonet.net,
fw@deneb.enyo.de, netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: Route cache performance tests
Date: Tue, 17 Jun 2003 22:49:50 +0200 [thread overview]
Message-ID: <16111.32494.113831.745019@robur.slu.se> (raw)
In-Reply-To: <20030617200721.GA25773@netnation.com>
Simon Kirby writes:
> I changed Juno to send from a single IP, but it only spat out about
> 330000 pps, which the dual Tigon3 Opteron box forwarded completely.
> In order to do a single flow forwarding test, I need to be able to create
> more input traffic somehow. Seeing as you wrote pktgen.c, maybe you
> could help in this department. :)
OK. See below.
> > Also think Simon used only /32 routes... I took "real" Internet-routing
> > and made a script so it can be used for experiments. I can make it available.
>
> Yes, I found that area less interesting since Dave M. fixed the hash
> buckets. But yes, the prefix scanning will slow it down some.
Well I don't think it's so easy as there are 33 zones with prefixes if
you have all the routes in one zone I'm not sure what happens thats why
I suggested the comparison.
> Erm. I can't get fib_stats2.pat to apply against 2.5.71, 2.5.71+davem's
> join-two-diffs patch, 2.4.21-rc7, or 2.5.71+davem's rtcache changes.
> What's it supposed to be against?
Sorry. Our production system and lab uses very patched 2.5.66
I'll make a patch for 2.5.71....
> If I start two threads on the sender (Xeon w/HT), I'm able to push 420000
> pps, which only partially starts to use NAPI on the Opteron box. Going
> to try 2.4 again for a comparison (note: 2.5 seems to have an opposite
> PCI scan order from 2.4 for the dual Tigon3s).
Not bad. Replace net/core/pktgen.c in 2.5.X with the version from
ftp://robur.slu.se/pub/Linux/net-development/pktgen-testing/
and edit pktgen.sh to suit your needs.
And see what you got. I'm interested since you are using both different
processors as NIC's. Also packet generation itself is interesting as
it tests driver/HW xmit-path.
Cheers.
--ro
next prev parent reply other threads:[~2003-06-17 20:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 7:57 Route cache performance tests Simon Kirby
2003-06-10 11:23 ` Jamal Hadi
2003-06-10 20:36 ` CIT/Paul
2003-06-10 13:34 ` Ralph Doncaster
2003-06-10 13:39 ` Jamal Hadi
2003-06-13 6:20 ` David S. Miller
2003-06-16 22:37 ` Simon Kirby
2003-06-16 22:44 ` David S. Miller
2003-06-16 23:09 ` Simon Kirby
2003-06-16 23:08 ` David S. Miller
2003-06-16 23:27 ` Simon Kirby
2003-06-16 23:49 ` Simon Kirby
2003-06-17 15:59 ` David S. Miller
2003-06-17 16:50 ` Robert Olsson
2003-06-17 16:50 ` David S. Miller
2003-06-17 17:29 ` Robert Olsson
2003-06-17 19:06 ` Mr. James W. Laferriere
2003-06-17 20:12 ` Robert Olsson
2003-06-17 20:07 ` Simon Kirby
2003-06-17 20:17 ` Martin Josefsson
2003-06-17 20:37 ` Simon Kirby
2003-06-17 20:36 ` David S. Miller
2003-06-17 20:51 ` Simon Kirby
2003-06-17 20:49 ` David S. Miller
2003-06-18 5:50 ` Pekka Savola
2003-06-17 20:49 ` Robert Olsson [this message]
2003-06-17 21:07 ` Simon Kirby
2003-06-17 22:50 ` Simon Kirby
2003-06-17 23:07 ` David S. Miller
2003-06-17 22:11 ` Ralph Doncaster
2003-06-17 22:08 ` 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=16111.32494.113831.745019@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=davem@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=hadi@shell.cyberus.ca \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=ralph+d@istop.com \
--cc=sim@netnation.com \
--cc=xerox@foonet.net \
/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).