netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: [RFC] driver adjusts qlen, increases CPU
Date: Fri, 04 Aug 2006 11:43:05 -0700	[thread overview]
Message-ID: <44D39539.5040805@hp.com> (raw)
In-Reply-To: <Pine.WNT.4.63.0605100905150.1804@jbrandeb-desk.amr.corp.intel.com>

Jesse Brandeburg wrote:
> So we've recently put a bit of code in our e1000 driver to decrease the 
> qlen based on the speed of the link.
> 
> On the surface it seems like a great idea.  A driver knows when the link 
> speed changed, and having a 1000 packet deep queue (the default for most 
> kernels now) on top of a 100Mb/s link (or 10Mb/s worst case for us) makes 
> for a *lot* of latency if many packets are queued up in the qdisc.
> 
> Problem we've seen is that setting this shorter queue causes a large spike 
> in cpu when transmitting using UDP:
> 
> 100Mb/s link
> txqueuelen: 1000 Throughput: 92.44 CPU: 5.00
> txqueuelen: 100 Throughput: 93.80 CPU: 61.59
> 
> Is this expected? any comments?

Triggering intra-stack flow-control perhaps?  Perhaps 10X more often 
than before if the queue is 1/10th what it was before?

Out of curiousity, how does the UDP socket's SO_SNDBUF compare to the 
queue depth?

rick jones

  reply	other threads:[~2006-08-04 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04 15:45 [RFC] driver adjusts qlen, increases CPU Jesse Brandeburg
2006-08-04 18:43 ` Rick Jones [this message]
2006-08-04 21:07   ` Jesse Brandeburg
2006-08-04 21:32     ` Rick Jones

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=44D39539.5040805@hp.com \
    --to=rick.jones2@hp.com \
    --cc=jesse.brandeburg@intel.com \
    --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).