From: Jakub Kicinski <kuba@kernel.org>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Network Development <netdev@vger.kernel.org>
Subject: Re: This is the fourth time I’ve tried to find what led to the regression of outgoing network speed and each time I find the merge commit 8c94ccc7cd691472461448f98e2372c75849406c
Date: Fri, 2 Feb 2024 18:32:59 -0800 [thread overview]
Message-ID: <20240202183259.33859154@kernel.org> (raw)
In-Reply-To: <881d47bf-5f5d-49d6-9502-3b22899eb253@infradead.org>
Thanks for the forward!
On Fri, 2 Feb 2024 17:16:41 -0800 Randy Dunlap wrote:
> >> When I copy files from one computer to another and kernel snapshot
> >> builded from commit 296455ade1fd I have 97-110MB/sec which is almost
> >> max speed of 1Gbps link.
> >> When I move to commit 9d1694dc91ce I have only 66-70MB/sec which is
> >> significantly slower.
There isn't that much networking in between the two.
Is any of the CPU cores at 100% when you are transferring the data on
the bad commit?
Do you have any iptables / nftables rules?
Are you using TLS in the transfer?
Did you try reverting f1172f3ee3a98754?
next prev parent reply other threads:[~2024-02-03 2:33 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 1:02 This is the fourth time I’ve tried to find what led to the regression of outgoing network speed and each time I find the merge commit 8c94ccc7cd691472461448f98e2372c75849406c Mikhail Gavrilov
2024-02-03 1:08 ` Rahul Rameshbabu
2024-02-03 1:15 ` Randy Dunlap
2024-02-03 1:16 ` Randy Dunlap
2024-02-03 2:32 ` Jakub Kicinski [this message]
2024-02-03 18:20 ` Christian A. Ehrhardt
2024-02-04 20:47 ` Christian A. Ehrhardt
2024-02-05 21:08 ` Mikhail Gavrilov
2024-02-06 11:26 ` Mathias Nyman
2024-02-06 16:12 ` Mikhail Gavrilov
2024-02-07 10:40 ` Mathias Nyman
2024-02-07 11:55 ` Mikhail Gavrilov
2024-02-08 9:25 ` Mathias Nyman
2024-02-08 10:32 ` Mikhail Gavrilov
2024-02-08 15:43 ` Mathias Nyman
2024-02-16 6:15 ` This is the fourth time Iâve " Linux regression tracking (Thorsten Leemhuis)
2024-02-19 9:41 ` This is the fourth time I’ve " Mikhail Gavrilov
2024-02-20 23:19 ` Mikhail Gavrilov
2024-02-20 23:41 ` Randy Dunlap
2024-02-20 23:43 ` Randy Dunlap
2024-02-21 13:44 ` Mathias Nyman
2024-02-26 5:45 ` This is the fourth time I've " Linux regression tracking (Thorsten Leemhuis)
2024-02-26 9:24 ` Mathias Nyman
2024-02-26 9:51 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-26 10:54 ` Mathias Nyman
2024-02-26 18:09 ` Thomas Gleixner
2024-02-27 17:08 ` mikhail.v.gavrilov
2024-02-27 17:23 ` Thomas Gleixner
[not found] ` <960fd112b294a902e1bea1fdd8e04a708a05cf45.camel@gmail.com>
2024-02-29 9:41 ` Mikhail Gavrilov
2024-03-04 14:10 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-21 6:48 ` This is the fourth time I’ve " Linux regression tracking #adding (Thorsten Leemhuis)
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=20240202183259.33859154@kernel.org \
--to=kuba@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=rdunlap@infradead.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