From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Data sitting and remaining in Send-Q
Date: Mon, 24 Dec 2001 21:17:26 +0100 [thread overview]
Message-ID: <20011224211726.H2461@lug-owl.de> (raw)
In-Reply-To: <20011224203828.G2461@lug-owl.de> <Pine.LNX.4.43.0112241507550.31883-100000@filesrv1.baby-dragons.com>
In-Reply-To: <Pine.LNX.4.43.0112241507550.31883-100000@filesrv1.baby-dragons.com>
On Mon, 2001-12-24 15:09:07 -0500, Mr. James W. Laferriere <babydr@baby-dragons.com>
wrote in message <Pine.LNX.4.43.0112241507550.31883-100000@filesrv1.baby-dragons.com>:
>
> Hello Jan , Is this possibly related to a ECN enabled host &
> somewhere in between a Non-ECN enabled (or a cisco router) ?
That would give a different result: "functional TCP connections" or
"non-functional TCP connections". Mine are between that. If data gets
sent in small chunks, everything is fine, but if it's a larger
transfer (more than one ethernet frame may transport???), write()
stalls (or non-blocking write returns), but data is kept in
Send-Q rather than being sent down to the client.
Well, my setup is a LAN, everything here is fully functional wrt.
ECN. I've never switched ECN off, and 2.4.x is running since ages
on the boxes around. So it's definitely *not* ECN in this case:-(
MfG, JBG
--
Jan-Benedict Glaw . jbglaw@lug-owl.de . +49-172-7608481
-- New APT-Proxy written in shell script --
http://lug-owl.de/~jbglaw/software/ap2/
next prev parent reply other threads:[~2001-12-24 20:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-24 17:01 Data sitting and remaining in Send-Q Jan-Benedict Glaw
2001-12-24 18:10 ` José Luis Domingo López
2001-12-24 19:00 ` Jan-Benedict Glaw
2001-12-24 19:38 ` Jan-Benedict Glaw
2001-12-24 20:09 ` Mr. James W. Laferriere
2001-12-24 20:17 ` Jan-Benedict Glaw [this message]
2001-12-24 20:44 ` Alex Bligh - linux-kernel
2001-12-24 21:34 ` Thorsten Kranzkowski
2001-12-24 21:58 ` Jan-Benedict Glaw
2001-12-24 21:56 ` Jan-Benedict Glaw
2001-12-25 0:43 ` Alex Bligh - linux-kernel
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=20011224211726.H2461@lug-owl.de \
--to=jbglaw@lug-owl.de \
--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