Netdev List
 help / color / mirror / Atom feed
From: Yinglin Sun <yinglin.s@gmail.com>
To: netdev@vger.kernel.org
Subject: [TCP_CA_CWR] Causes for entering TCP_CA_CWR state with 0 retransmissions
Date: Tue, 14 Jul 2009 14:38:07 -0400	[thread overview]
Message-ID: <46bf9ede0907141138q3b665aefv46a18591c3cfc2ce@mail.gmail.com> (raw)

Hi,

I have a question about tcp_ca_state "TCP_CA_CWR".  Under what
circumstances does it enter this state?
I'm doing some experiments and have trace from tcp_info. From tcp_info
trace, I found that many places show ca_state is 2 (TCP_CA_CWR). Under
this state, the congestion window size decreases but the total number
of retransmissions is still 0.

I got some explanation from a very old message posted in 2003:
TCP_CA_CWR: The congestion window should be reduced due to some
congestion notification event, which can be ECN, ICMP source quench,
or local device congestion. Both sender and receiver don't have ECN
enabled, so ECN is not the case. ICMP source quench is so out-of-date
with RFC 1812 saying the routers should not issue these packets. So it
might be caused by local congestion. But this post is too old, almost
done 6 years ago. So I want to check if there are other possible
causes in today's kernel leading to TCP_CA_CWR with 0 retransmissions?

I need to find the exact cause for this phenomena, local congestion,
or other possible causes. Any hint will be very helpful for me.

Thanks a lot!

Yinglin

             reply	other threads:[~2009-07-14 18:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 18:38 Yinglin Sun [this message]
2009-07-14 18:42 ` [TCP_CA_CWR] Causes for entering TCP_CA_CWR state with 0 retransmissions David Miller
2009-07-14 19:12   ` Yinglin Sun
2009-07-14 19:15     ` David Miller
2009-07-14 19:49       ` Yinglin Sun
2009-07-14 19:53         ` David Miller
2009-07-14 19:58           ` Yinglin Sun

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=46bf9ede0907141138q3b665aefv46a18591c3cfc2ce@mail.gmail.com \
    --to=yinglin.s@gmail.com \
    --cc=netdev@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