Messages in this thread | | | Subject | Re: select() doesn't respect SO_RCVLOWAT ? | From | Alan Cox <> | Date | Mon, 14 Mar 2005 13:24:24 +0000 |
| |
On Gwe, 2005-03-11 at 20:26, Felix Matathias wrote: > Dear Alan, > > I am positive. I can setsockopt, and then, getsockopt returns the value > that I requested.
Ok I misremembered - its SNDLOWAT that is locked to one in Linux.
> Stevens very clearly states that SO_RCVLOWAT has a direct impact on > select() and I assumed that this would be the case for Linux. > What is the rationale for not complying with that ? Is it the micromanagement > of select() that you dislike ? Isn't a significant reduction in the > amount of read operations a real gain in high speed networking ?
I believe since we implement SO_SNDLOWAT that its a bug. Stevens and 1003.1g both agree with your expectations. The right list is probably netdev@oss.sgi.com however.
Alan
- 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/
| |