General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Hal Murray <hmurray@megapathdsl.net>
To: bloat@lists.bufferbloat.net
Cc: Hal Murray <hmurray@megapathdsl.net>
Subject: [Bloat] SO_SNDBUF and SO_RCVBUF
Date: Wed, 22 Apr 2015 12:10:56 -0700	[thread overview]
Message-ID: <20150422191056.9C7AC406057@ip-64-139-1-69.sjc.megapath.net> (raw)


> As I understand it (I thought) SO_SNDBUF and SO_RCVBUF are socket buffers
> for the application layer, they do not change the TCP window size either
> send or receive. Which is perhaps why they aren't used much. They don't do
> much good in iperf that's for sure! Might be wrong, but I agree with the
> premise - auto-tuning should work.

I sure expect them to do the obvious thing.

man 7 socket says:

       SO_SNDBUF
              Sets  or gets the maximum socket send buffer in bytes.

It doesn't actually say that turns into the TCP window size.

On Linux, there is a factor of 2 for overhead and whatever.

man tcp says:
      TCP uses the extra space for administrative purposes and inter-
       nal kernel structures, and the /proc file  values  reflect  the  larger
       sizes  compared  to the actual TCP windows.

So it looks like the number you feed it turns into the window size.

A few quick tests with netperf confirm that it is doing something close to 
what I expect but I haven't fired up tcpdump to verify that the window size 
is what I asked for.  netperf does print out values that are 2x what I asked 
for.

Yuck.  (That's Yuck at Linux, not netperf.)


-- 
These are my opinions.  I hate spam.




             reply	other threads:[~2015-04-22 19:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-22 19:10 Hal Murray [this message]
2015-04-22 19:26 ` Rick Jones
2015-04-22 19:28 ` Dave Taht
2015-04-22 21:02   ` Eric Dumazet
2015-04-22 21:05     ` Rick Jones
2015-04-22 21:46       ` Eric Dumazet
2015-04-22 22:20         ` Simon Barber
2015-04-22 23:08           ` Eric Dumazet
2015-04-24  4:37       ` Dave Taht
2015-04-24  4:40         ` Dave Taht
2015-04-24 13:50           ` Eric Dumazet
2015-04-24 14:34             ` Dave Taht
2015-04-24 16:31             ` Rick Jones
2015-04-24 18:41               ` Eric Dumazet
2015-04-24  5:23         ` Eric Dumazet
2015-04-22 21:07     ` Steinar H. Gunderson
2015-04-22 21:42       ` Eric Dumazet
2015-04-22 21:47         ` Dave Taht
2015-04-22 22:11         ` Steinar H. Gunderson

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

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150422191056.9C7AC406057@ip-64-139-1-69.sjc.megapath.net \
    --to=hmurray@megapathdsl.net \
    --cc=bloat@lists.bufferbloat.net \
    /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