From: Tomi Lapinlampi <lapinlam@intellitel.com>
To: linux-kernel@vger.kernel.org
Subject: [PROBLEM] socket buffering problem in 2.2.19
Date: Wed, 2 May 2001 11:30:30 +0300 [thread overview]
Message-ID: <20010502113027.T29301@intellitel.com> (raw)
Hi,
There seems to be some kind of a buffering problem in the 2.2.19
kernel. The following sequence of system calls on a nonblocking TCP
socket (on the client side) generates a broken pipe:
write(2) HTTP REQUEST read(2)
2. HTTP client --------------------> HTTP Server
HTTP RESPONSE write(2)
3. HTTP client <--------------------- HTTP Server
shutdown(2), close(2)
4. HTTP client <--------------------- HTTP Server
select(2) returns,
read(2) => broken pipe, HTTP response is lost
5. HTTP client <----X
The client in this situation is a bit sluggish and sometimes does not have
time to read the data before the server has called shutdown and close
(and the client receives a TCP FIN).
The Linux 2.4.3 kernel and Solaris 7 & 8 seem to perform the buffering of
data ok on the client side.
Any ideas or suggestions ( other than upgrade to 2.4 :-) ) ?
Regards, Tomi
reply other threads:[~2001-05-02 8:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010502113027.T29301@intellitel.com \
--to=lapinlam@intellitel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox