From: spy9599 <spy9599@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Is TCP CA_LOSS to CA_RECOVERY possible
Date: Wed, 17 Jul 2002 09:18:34 -0700 (PDT) [thread overview]
Message-ID: <20020717161834.12994.qmail@web14806.mail.yahoo.com> (raw)
Hi,
I have a question regrading the TCP implementation. I
am not subscribed to this list, so please cc your
response.
In the present TCP (2.5.x) implementation, the TCP
sender never exits TCP_CA_Loss state until all packets
upto high_seq are acknowledged. But lets say while
doing retransmissions, some packet less than high_seq
are lost again. Ideally the TCP sender should just
enter fast retransmit and fast recovery, but from the
present implementation it seems the only way to come
out of it is after a timeout.
Could somebody explain this to me please.
Thank you very much.
Best Regards
--SPY
__________________________________________________
Do You Yahoo!?
Yahoo! Autos - Get free new car price quotes
http://autos.yahoo.com
next reply other threads:[~2002-07-17 16:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 16:18 spy9599 [this message]
2002-07-17 16:44 ` Mika Liljeberg
2002-07-17 17:35 ` kuznet
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=20020717161834.12994.qmail@web14806.mail.yahoo.com \
--to=spy9599@yahoo.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
all inboxes | Powered by JetHome®