From: Vijay Subramanian <subramanian.vijay@gmail.com>
To: Anatoly Sivov <mm05@mail.ru>
Cc: netdev@vger.kernel.org
Subject: Re: tcp_mtu_probe implementation details
Date: Tue, 20 Dec 2011 14:33:01 -0800 [thread overview]
Message-ID: <CAGK4HS93u=3muZu_rkqK7FSacTHUytK5H6_dMNo_uOQY738R_g@mail.gmail.com> (raw)
In-Reply-To: <op.v6s5j2i0fzo5me@stalin>
> The other question is about size_needed variable.
> It is assigned to value probe_size + (tp->reordering + 1) * tp->mss_cache
> And that is not clear for me.
> What is this "(tp->reordering + 1) * tp->mss_cache" addition?
>
I think the idea is that you want enough bytes in the write_queue so
that even if the probe is lost, the sender will get an ack even if
there is reordering in the network. Without sufficient bytes, the
probe will not be sent. This is what I make of the code but I could be
wrong.
Regards,
Vijay
next prev parent reply other threads:[~2011-12-20 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 21:49 tcp_mtu_probe implementation details Anatoly Sivov
2011-12-20 22:33 ` Vijay Subramanian [this message]
2011-12-21 9:50 ` Anatoly Sivov
2011-12-24 15:03 ` John Heffner
2011-12-24 16:15 ` Anatoly Sivov
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='CAGK4HS93u=3muZu_rkqK7FSacTHUytK5H6_dMNo_uOQY738R_g@mail.gmail.com' \
--to=subramanian.vijay@gmail.com \
--cc=mm05@mail.ru \
--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).