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: <20130430011112.GA1504@dvomlehn-z8.spacex.com>
Date:	Mon, 29 Apr 2013 18:11:12 -0700
From:	David VomLehn <David.VomLehn@...cex.com>
To:	<netdev@...r.kernel.org>
Subject: What does socket option SO_SNDBUF mean?

I've been asked how the socket option SO_SNDBUF should be used to avoid
blocking by writing too many bytes to a socket. This amounts to asking
how to interpret the SO_SNDBUF value. After looking through the networking
code for various kernel versions, it looks like the amount of overhead
included and how it is used is variable.

So:
1.	How *should* SO_SNDBUF be interpreted?
2.	Is it appropriate to use it to avoid blocking of socket writes?
3.	Does it have other uses besides giving a very fuzzy idea of
	socket writes will block?
-- 
David VL
--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ