From: Eric Dumazet <eric.dumazet@gmail.com>
To: Yuchung Cheng <ycheng@google.com>, Deepti Raghavan <deeptir@mit.edu>
Cc: David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Neal Cardwell <ncardwell@google.com>
Subject: Re: [PATCH net-next] tcp: expose both send and receive intervals for rate sample
Date: Mon, 9 Jul 2018 10:02:53 -0700 [thread overview]
Message-ID: <88db8e3d-62da-38e6-2eee-a472d3eaa103@gmail.com> (raw)
In-Reply-To: <CAK6E8=drT8YpzmFNab07nCvOH5WnxxDWj+P+9cO4Yzhd_Y=BaA@mail.gmail.com>
On 07/09/2018 09:23 AM, Yuchung Cheng wrote:
> On Mon, Jul 9, 2018 at 9:05 AM, Deepti Raghavan <deeptir@mit.edu> wrote:
>> Congestion control algorithms, which access the rate sample
>> through the tcp_cong_control function, only have access to the maximum
>> of the send and receive interval, for cases where the acknowledgment
>> rate may be inaccurate due to ACK compression or decimation. Algorithms
>> may want to use send rates and receive rates as separate signals.
>>
>> Signed-off-by: Deepti Raghavan <deeptir@mit.edu>
> Acked-by: Yuchung Cheng <ycheng@google.com>
Okay, but please send a non HTML mail, otherwise the mail does not reach netdev@,
nor https://patchwork.ozlabs.org/project/netdev/list/
next prev parent reply other threads:[~2018-07-09 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKOGndb391n16rVhudpf4C5TWPikE7Oj9LywZ4f-v_YCr=Be=g@mail.gmail.com>
2018-07-09 16:23 ` [PATCH net-next] tcp: expose both send and receive intervals for rate sample Yuchung Cheng
2018-07-09 17:02 ` Eric Dumazet [this message]
2018-07-09 17:53 Deepti Raghavan
2018-07-09 18:09 ` Neal Cardwell
2018-07-09 18:11 ` Eric Dumazet
2018-07-12 6:02 ` David Miller
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=88db8e3d-62da-38e6-2eee-a472d3eaa103@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=deeptir@mit.edu \
--cc=edumazet@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.com \
/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).