netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Neal Cardwell <ncardwell@google.com>, Yuchung Cheng <ycheng@google.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Lawrence Brakmo <brakmo@fb.com>, Netdev <netdev@vger.kernel.org>,
	Kernel Team <kernel-team@fb.com>,
	ast@fb.com, Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH net-next] tcp: ack immediately when a cwr packet arrives
Date: Tue, 24 Jul 2018 10:26:32 -0700	[thread overview]
Message-ID: <e420d50e-4b4c-1009-6e4d-79aae2899c27@gmail.com> (raw)
In-Reply-To: <CADVnQynbJPtHSJuYoS6fEKdo-2Q_P4VXAa=ytz+NHMM+0dcLmA@mail.gmail.com>



On 07/24/2018 10:12 AM, Neal Cardwell wrote:
> On Tue, Jul 24, 2018 at 1:07 PM Yuchung Cheng <ycheng@google.com> wrote:
>>
>> On Mon, Jul 23, 2018 at 7:23 PM, Daniel Borkmann <daniel@iogearbox.net> wrote:
>>> Should this go to net tree instead where all the other fixes went?
>> I am neutral but this feels more like a feature improvement
> 
> I agree this feels like a feature improvement rather than a bug fix.

Agreed

Signed-off-by: Eric Dumazet <edumazet@google.com>

  reply	other threads:[~2018-07-24 18:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24  0:49 [PATCH net-next] tcp: ack immediately when a cwr packet arrives Lawrence Brakmo
2018-07-24  2:15 ` Neal Cardwell
2018-07-24  2:23   ` Daniel Borkmann
2018-07-24 17:06     ` Yuchung Cheng
2018-07-24 17:12       ` Neal Cardwell
2018-07-24 17:26         ` Eric Dumazet [this message]
2018-07-24 17:42         ` Lawrence Brakmo
2018-07-25  1:57           ` Neal Cardwell
2018-07-25 23:21             ` 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=e420d50e-4b4c-1009-6e4d-79aae2899c27@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=ast@fb.com \
    --cc=brakmo@fb.com \
    --cc=daniel@iogearbox.net \
    --cc=kernel-team@fb.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).