Re: [PATCH] Properly handle Linux TCP socket options

2013-01-22 Thread John Baldwin
On Monday, January 21, 2013 2:55:22 pm Alexander Leidinger wrote: > On Sat, 19 Jan 2013 11:26:13 -0500 John Baldwin wrote: > > > The current setsockopt() wrapper for the Linux ABI claims that Linux > > and FreeBSD use the same values for TCP socket options. This is true > > for TCP_NODELAY and T

Re: [PATCH] Properly handle Linux TCP socket options

2013-01-21 Thread Alexander Leidinger
On Sat, 19 Jan 2013 11:26:13 -0500 John Baldwin wrote: > The current setsockopt() wrapper for the Linux ABI claims that Linux > and FreeBSD use the same values for TCP socket options. This is true > for TCP_NODELAY and TCP_MAXSEG but not for any other options. This > patch adds a mapping routin

[PATCH] Properly handle Linux TCP socket options

2013-01-19 Thread John Baldwin
The current setsockopt() wrapper for the Linux ABI claims that Linux and FreeBSD use the same values for TCP socket options. This is true for TCP_NODELAY and TCP_MAXSEG but not for any other options. This patch adds a mapping routine for TCP options similar to that used for other socket option