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 <netdev@vger.kernel.org>
Subject: Re: RFC:  Removing busy-spin in pktgen.
Date: Tue, 24 Oct 2006 09:28:35 -0700	[thread overview]
Message-ID: <453E3F33.1090709@candelatech.com> (raw)
In-Reply-To: <17725.55765.509953.762136@robur.slu.se>

Robert Olsson wrote:
> Ben Greear writes:
>  > 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?
>
>  Hello!
>
>  So question is, pktgen hooks in netif_wake_queue or let pktgen busy-spin?
>
>  My first instinct is to avoid the hook in general code and pktgen let spin 
>  to only affect testing.
>   
Ok.  For my testing, I often run pktgen at slower speeds and need to run 
other applications
with good performance as well, so it hurts to give pktgen an entire CPU 
to just spin.  I'm
going to go ahead and port over the no-spin logic and hooks, but I'll 
try to keep that patch
easily separated from the rest of the changes I make to pktgen so 
perhaps the other changes
can be incorporated.

Thanks,
Ben

>  
>  Cheers.
> 					--ro
>   


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



      parent reply	other threads:[~2006-10-24 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-24  0:02 RFC: Removing busy-spin in pktgen Ben Greear
2006-10-24  9:16 ` 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 [this message]

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=453E3F33.1090709@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).