From: "Mohamed Abuelfotoh, Hazem" <abuehaze@amazon.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Eric Dumazet <edumazet@google.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"ycheng@google.com" <ycheng@google.com>,
"ncardwell@google.com" <ncardwell@google.com>,
"weiwan@google.com" <weiwan@google.com>,
"Strohman, Andy" <astroh@amazon.com>,
"Herrenschmidt, Benjamin" <benh@amazon.com>
Subject: Re: [PATCH net-next] tcp: optimise receiver buffer autotuning initialisation for high latency connections
Date: Mon, 7 Dec 2020 17:54:31 +0000 [thread overview]
Message-ID: <D78D31DF-F032-4EFB-BB79-31750797908D@amazon.com> (raw)
In-Reply-To: <X85qX19mo5XesW8b@kroah.com>
>5.4.0-rc6 is a very old and odd kernel to be doing anything with. Are
>you sure you don't mean "5.10-rc6" here?
I was able to reproduce it on the latest mainline kernel as well so anything newer than 4.19.85 is just broken.
Thank you.
Hazem
On 07/12/2020, 17:45, "Greg KH" <gregkh@linuxfoundation.org> wrote:
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
On Mon, Dec 07, 2020 at 04:34:57PM +0000, Mohamed Abuelfotoh, Hazem wrote:
> 100ms RTT
>
> >Which exact version of linux kernel are you using ?
> On the receiver side I could see the issue with any mainline kernel
> version >=4.19.86 which is the first kernel version that has patches
> [1] & [2] included. On the sender I am using kernel 5.4.0-rc6.
5.4.0-rc6 is a very old and odd kernel to be doing anything with. Are
you sure you don't mean "5.10-rc6" here?
thanks,
greg k-h
Amazon Web Services EMEA SARL, 38 avenue John F. Kennedy, L-1855 Luxembourg, R.C.S. Luxembourg B186284
Amazon Web Services EMEA SARL, Irish Branch, One Burlington Plaza, Burlington Road, Dublin 4, Ireland, branch registration number 908705
next prev parent reply other threads:[~2020-12-07 17:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 18:06 [PATCH net-next] tcp: optimise receiver buffer autotuning initialisation for high latency connections Hazem Mohamed Abuelfotoh
2020-12-04 18:19 ` Mohamed Abuelfotoh, Hazem
2020-12-04 18:41 ` Eric Dumazet
[not found] ` <3F02FF08-EDA6-4DFD-8D93-479A5B05E25A@amazon.com>
2020-12-07 15:25 ` Eric Dumazet
2020-12-07 16:09 ` Mohamed Abuelfotoh, Hazem
2020-12-07 16:22 ` Eric Dumazet
2020-12-07 16:33 ` Neal Cardwell
2020-12-07 17:08 ` Eric Dumazet
2020-12-07 20:09 ` Mohamed Abuelfotoh, Hazem
2020-12-07 23:22 ` Eric Dumazet
2020-12-07 17:16 ` Mohamed Abuelfotoh, Hazem
2020-12-07 17:27 ` Eric Dumazet
2020-12-08 16:28 ` Mohamed Abuelfotoh, Hazem
2020-12-08 16:30 ` Mohamed Abuelfotoh, Hazem
2020-12-08 16:46 ` Eric Dumazet
2020-12-07 16:34 ` Mohamed Abuelfotoh, Hazem
2020-12-07 17:46 ` Greg KH
2020-12-07 17:54 ` Mohamed Abuelfotoh, Hazem [this message]
2020-12-04 19:10 ` Eric Dumazet
2020-12-04 21:28 ` Neal Cardwell
2020-12-07 11:46 ` [PATCH net] tcp: fix receive buffer autotuning to trigger for any valid advertised MSS Hazem Mohamed Abuelfotoh
2020-12-07 18:53 ` Jakub Kicinski
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=D78D31DF-F032-4EFB-BB79-31750797908D@amazon.com \
--to=abuehaze@amazon.com \
--cc=astroh@amazon.com \
--cc=benh@amazon.com \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=weiwan@google.com \
--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).