From: clock@beton.btnet.cz
To: linux-kernel@vger.kernel.org
Subject: TCP stack misbehaviour?
Date: Sun, 8 Apr 2001 16:19:33 +0200 [thread overview]
Message-ID: <20010408161933.A223@beton.btnet.cz> (raw)
The TCP stack in the linux kernel behaves this way:
I have got a FULL-DUPLEX 28.800kbps channel with BER <= 1*10-9
a) I start a long TCP connection in one direction
b) After 5 minutes I start another connection in the opposite direction
The second connection rusn for about half a minute, then converges to 0
throughtput. After several minutes, another 30 seconds of transmission ocuur.
The data path in the direction that should be used for this connection is
empty, except for occasional ACKs. The utilization of the channel is about 4%.
I would expect that both channels would be used for at least 95%. Instead, only
one is used.
Is this a bug of Linux kernel TCP stack, or a bug in the algorithm presented
in the appropriate RFC?
Isn't UDP more suitable for data transfers?
--
Karel Kulhavy http://atrey.karlin.mff.cuni.cz/~clock
next reply other threads:[~2001-04-08 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-08 14:19 clock [this message]
2001-04-08 17:02 ` kuznet
[not found] <000701c0c046$17001920$5517fea9@local>
2001-04-08 16:09 ` clock
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=20010408161933.A223@beton.btnet.cz \
--to=clock@beton.btnet.cz \
--cc=clock@ghost.btnet.cz \
--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
all inboxes | Powered by JetHome®