From: Andi Kleen <andi@firstfloor•org>
To: Li Yu <raise.sail@gmail•com>
Cc: "netdev\@vger.kernel.org" <netdev@vger•kernel.org>
Subject: Re: TCP always advertises zero window.
Date: Mon, 25 Oct 2010 20:18:14 +0200 [thread overview]
Message-ID: <87tyka3zmh.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4CBFE924.2060103@gmail.com> (Li Yu's message of "Thu, 21 Oct 2010 15:17:56 +0800")
Li Yu <raise.sail@gmail•com> writes:
>
> According to source code, only MTU probing success and receive some non-zero length of L7 payload could grow tcp_sock->rcv_ssthresh. Because of we turn off MTU probing and TCP only received some zero-window probe from another end, so it seem that we have not any chance to update tcp_sock->rcv_ssthresh at all, so a dead loop come here.
The question is why are you turning off MTU probing?
-Andi
prev parent reply other threads:[~2010-10-25 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 7:17 TCP always advertises zero window Li Yu
2010-10-25 18:18 ` Andi Kleen [this message]
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=87tyka3zmh.fsf@basil.nowhere.org \
--to=andi@firstfloor$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=raise.sail@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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