From: Ben Greear <greearb@candelatech.com>
To: NetDev <netdev@vger.kernel.org>
Cc: Robert Olsson <Robert.Olsson@data.slu.se>
Subject: RFC: Removing busy-spin in pktgen.
Date: Mon, 23 Oct 2006 17:02:52 -0700 [thread overview]
Message-ID: <453D582C.9020705@candelatech.com> (raw)
I'm planning to re-merge my long-lost pktgen branch with the kernel
tree's pktgen.
I believe the main difference is that my out-of-tree pktgen does not do the
busy-spin, but waits on a queue for the net-device to wake it's tx-queue
when over-driving a NIC.
To implement this, I added a hook in the netdev-wake-queue logic and let
pktgen register itself as interested....
Is there any interest in adding this sort of feature to the official
pktgen?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2006-10-24 0:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 0:02 Ben Greear [this message]
2006-10-24 9:16 ` RFC: Removing busy-spin in pktgen Robert Olsson
2006-10-24 10:14 ` David Miller
2006-10-24 16:34 ` Ben Greear
2006-10-24 22:09 ` David Miller
2006-10-24 16:28 ` Ben Greear
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=453D582C.9020705@candelatech.com \
--to=greearb@candelatech.com \
--cc=Robert.Olsson@data.slu.se \
--cc=netdev@vger.kernel.org \
/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).