netdev - Socket send-buffer auto-sizing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <4FD0EC01.3020300@candelatech.com>
Date:	Thu, 07 Jun 2012 10:59:29 -0700
From:	Ben Greear <greearb@...delatech.com>
To:	netdev <netdev@...r.kernel.org>
Subject: Socket send-buffer auto-sizing

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@...delatech.com>
Candela Technologies Inc  http://www.candelatech.com

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html