Messages in this thread | | | Subject | Re: setsockopt(SOL_SOCKET, SO_SNDBUF) broken on 2.4.18? | Date | Tue, 26 Feb 2002 00:11:30 +0000 (UTC) | From | (Ton Hospel) |
| |
In article <E16_Tly-0006Va-00@the-village.bc.nu>, Alan Cox <alan@lxorguk.ukuu.org.uk> writes: >> to verify what the kernel has set, I read TWICE as much the amount used >> for the set. That is, if I set 8192, I read 16384. Therefore, to set >> the correct size, I need to half the parameter first. >> Is this a known bug? Is it setsockopt or getsockopt which returns the >> wrong size? > > Neither. You asked for 8K the kernel allows a bit more for BSD compatibility > and other things. You query and it gives back the size it chose
it's still insane it doesn't use the same fudge factor in both directions. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |