netdev - Re: setsockopt()

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080709052534.GA8157@2ka.mipt.ru>
Date:	Wed, 9 Jul 2008 09:25:35 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Bill Fink <billfink@...dspring.com>
Cc:	Stephen Hemminger <stephen.hemminger@...tta.com>,
	Roland Dreier <rdreier@...co.com>,
	David Miller <davem@...emloft.net>, aglo@...i.umich.edu,
	shemminger@...tta.com, netdev@...r.kernel.org, rees@...ch.edu,
	bfields@...ldses.org
Subject: Re: setsockopt()

On Tue, Jul 08, 2008 at 06:05:00PM -0400, Bill Fink (billfink@...dspring.com) wrote:
> BTW I believe there is one other important difference between the way
> the tcp_rmem/tcp_wmem autotuning parameters are handled versus the way
> the rmem_max/wmem_max parameters are used when explicitly setting the
> socket buffer sizes.  I believe the tcp_rmem/tcp_wmem autotuning maximum
> parameters are hard limits, with the default maximum tcp_rmem setting
> being ~170 KB and the default maximum tcp_wmem setting being 128 KB.

Maximum tcp_wmem depends on amount of available RAM, but at least 64k.
Maybe Reoland's distro set hard limit just to 128k...

-- 
	Evgeniy Polyakov
--
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