netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>, netdev@vger.kernel.org
Subject: Re: [RFC] driver adjusts qlen, increases CPU
Date: Fri, 04 Aug 2006 14:32:52 -0700	[thread overview]
Message-ID: <44D3BD04.7040806@hp.com> (raw)
In-Reply-To: <4807377b0608041407r3d27805aw649b4103bca97614@mail.gmail.com>

>> Out of curiousity, how does the UDP socket's SO_SNDBUF compare to the
>> queue depth?
> 
> 
> forgive my ignorance, how do i measure that?

getsockopt(SO_SNDBUF)?  I was just casting about on the possiblity that 
interactions between the depth of that queue and how much can be kept in 
the SO_SNDBUF might be involved.

rick jones

      reply	other threads:[~2006-08-04 21:32 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
2006-08-04 21:07   ` Jesse Brandeburg
2006-08-04 21:32     ` Rick Jones [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=44D3BD04.7040806@hp.com \
    --to=rick.jones2@hp.com \
    --cc=jesse.brandeburg@gmail.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).