From: Fan Du <fengyuleidian0615@gmail.com>
To: John Heffner <johnwheffner@gmail.com>
Cc: Fan Du <fan.du@intel.com>, David Miller <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 3/4] ipv4: Use probe_size to check write queue data length
Date: Wed, 18 Mar 2015 09:37:05 +0800 [thread overview]
Message-ID: <5508D6C1.2020302@gmail.com> (raw)
In-Reply-To: <CABrhC0=+c1XpVZZpRyhrFJmUwdf1mp1RtWUh+jV-Mg3GXDAqwQ@mail.gmail.com>
于 2015年03月10日 20:26, John Heffner 写道:
> NACK. From RFC4821:
>
> In addition, the timely loss detection algorithms in most protocols
> have pre-conditions that SHOULD be satisfied before sending a probe.
> For example, TCP Fast Retransmit is not robust unless there are
> sufficient segments following a probe; that is, the sender SHOULD
> have enough data queued and sufficient receiver window to send the
> probe plus at least Tcprexmtthresh [RFC2760] additional segments.
> This restriction may inhibit probing in some protocol states, such as
> too close to the end of a connection, or when the window is too
> small.
>
Thanks for pointing this out for me.
My limit understanding is the extra segments is used to trigger fast retransmit,
and the conditions is the count of duplicate ack. Then why needs an extra one more
segment here besides 'reordering' segment to trigger this?
size_needed = probe_size + (tp->reordering + 1) * tp->mss_cache;
^^^
btw, any comments for the rest of patches?
--
天下英雄出我辈,一入江湖岁月催。
鸿图霸业谈笑间,不胜人生一场醉。
提剑跨骑挥鬼雨,白骨如山鸟惊飞。
尘世如潮人如水,只叹江湖几人回。
来,干了这碗酒,接着解BUG!
next prev parent reply other threads:[~2015-03-18 1:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 9:16 [PATCH net-next 0/4] Fix for TCP PMTU Fan Du
2015-03-10 9:16 ` [PATCH net-next 1/4] ipv4: Rename tcp_mtu_probing to tcp_blackhole_probe Fan Du
2015-03-10 9:16 ` [PATCH net-next 2/4] ipv4: Correct two conditions checking when buildig nskb Fan Du
2015-03-18 12:44 ` John Heffner
2015-03-10 9:16 ` [PATCH net-next 3/4] ipv4: Use probe_size to check write queue data length Fan Du
2015-03-10 12:26 ` John Heffner
2015-03-18 1:37 ` Fan Du [this message]
2015-03-18 12:41 ` John Heffner
2015-03-10 9:16 ` [PATCH net-next 4/4] ipv4: clamp sysctl_tcp_probe_threshold Fan Du
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=5508D6C1.2020302@gmail.com \
--to=fengyuleidian0615@gmail.com \
--cc=davem@davemloft.net \
--cc=fan.du@intel.com \
--cc=johnwheffner@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;
as well as URLs for NNTP newsgroup(s).