public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft•net>
To: Robert.Olsson@data•slu.se
Cc: greearb@candelatech•com, netdev@vger•kernel.org
Subject: Re: RFC: Removing busy-spin in pktgen.
Date: Tue, 24 Oct 2006 03:14:55 -0700 (PDT)	[thread overview]
Message-ID: <20061024.031455.55723788.davem@davemloft.net> (raw)
In-Reply-To: <17725.55765.509953.762136@robur.slu.se>

From: Robert Olsson <Robert.Olsson@data•slu.se>
Date: Tue, 24 Oct 2006 11:16:05 +0200

>  My first instinct is to avoid the hook in general code and pktgen let spin 
>  to only affect testing.

Mine too.

Why make everyone in the world make that check in netif_wake_queue(),
or wherever, when %99.99999999999 of the time it'll never be used?

  reply	other threads:[~2006-10-24 10:14 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 [this message]
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=20061024.031455.55723788.davem@davemloft.net \
    --to=davem@davemloft$(echo .)net \
    --cc=Robert.Olsson@data$(echo .)slu.se \
    --cc=greearb@candelatech$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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