From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Felix Matathias <felix@nevis.columbia.edu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: select() doesn't respect SO_RCVLOWAT ?
Date: Mon, 14 Mar 2005 13:24:24 +0000 [thread overview]
Message-ID: <1110806662.15927.108.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0503111434040.30914@shang.nevis.columbia.edu>
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
next prev parent reply other threads:[~2005-03-14 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 21:58 select() doesn't respect SO_RCVLOWAT ? Felix Matathias
2005-03-11 5:43 ` Willy Tarreau
2005-03-11 5:43 ` Willy Tarreau
2005-03-11 19:09 ` Alan Cox
2005-03-11 19:09 ` Alan Cox
2005-03-11 20:26 ` Felix Matathias
2005-03-14 13:24 ` Alan Cox [this message]
2005-03-14 13:34 ` YOSHIFUJI Hideaki / 吉藤英明
2005-03-14 13:24 ` Alan Cox
2005-03-22 2:30 ` Robert White
2005-03-11 20:26 ` Felix Matathias
-- strict thread matches above, loose matches on Subject: below --
2005-03-10 21:58 Felix Matathias
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1110806662.15927.108.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=felix@nevis.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.