All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: netdev <netdev@vger.kernel.org>
Subject: Socket send-buffer auto-sizing
Date: Thu, 07 Jun 2012 10:59:29 -0700	[thread overview]
Message-ID: <4FD0EC01.3020300@candelatech.com> (raw)

I'm continuing to test one-way tcp streams in 3.5.0-rc1 on
a wifi network.

When I do not specify a send buffer size, and thus use the kernel
defaults, max speed is about 77Mbps.

When I specify 512KB send-buffer, I get speeds up to 185Mbps.

When set to 1MB, I get about 198Mbps (and setting higher does not
increase the throughput after this).

This is without any 'delack' patches applied.

My question is:  Should the kernel auto-tuner work better?

I seem to recall a comments from some years ago that applications
should no longer attempt to tune send/recv buffers because the kernel
was smart enough to get it at least mostly right.

Thanks,
Ben

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

                 reply	other threads:[~2012-06-07 17:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4FD0EC01.3020300@candelatech.com \
    --to=greearb@candelatech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.