From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Ben Greear <greearb@candelatech.com>
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
"'netdev@oss.sgi.com'" <netdev@oss.sgi.com>
Subject: Re: 2.6.7 tulip performance (with NAPI)
Date: Thu, 7 Oct 2004 23:11:47 +0200 [thread overview]
Message-ID: <16741.45331.743721.822091@robur.slu.se> (raw)
In-Reply-To: <41649425.1010102@candelatech.com>
Ben Greear writes:
>
> int pg_notify_queue_woken(struct net_device* dev) {
> struct pktgen_interface_info* info = dev->nqw_data;
> if (info && info->pg_thread->sleeping) {
> if (getRelativeCurNs() > (info->next_tx_ns - 1000)) {
> /* See if we should wake up the thread, wake
> * slightly early (1000 ns)
> */
> info->pg_thread->sleeping = 0;
> wake_up_interruptible(&(info->pg_thread->queue));
> }
> }
> return 0;
> }
Interesting... I got requests for higher performance in flow/DoS testing
to be really useful. Probably only preallocation will help here.
To be really aggressive we could hack the driver TX handling so at TX
interrupt also refills/refresh the ring but it's not a general solution.
I guess you can use an existing qdisc via dev_queue_xmit() or something
to save CPU in your case.
I was sending wire rate from 10 GIGE NIC's from a DUAL XEON w. HT
I'm interested if anyone has done any pktgen performance tests with
w. S2IO or other 10G card we need to upgrade the lab equipment.
Both 64 byte pkts and MTU sized pkts is interesting. Anyone?
Cheers.
--ro
next prev parent reply other threads:[~2004-10-07 21:11 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
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 [this message]
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=16741.45331.743721.822091@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=greearb@candelatech.com \
--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).