From: Thomas Gleixner <tglx@linutronix.de>
To: mikhail.v.gavrilov@gmail.com,
Mathias Nyman <mathias.nyman@linux.intel.com>,
Linux regressions mailing list <regressions@lists.linux.dev>
Cc: "Christian A. Ehrhardt" <lk@c--e.de>,
niklas.neronin@linux.intel.com,
Linux List Kernel Mailing <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, x86@kernel.org,
netdev@vger.kernel.org, Randy Dunlap <rdunlap@infradead.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: Tue, 27 Feb 2024 18:23:51 +0100 [thread overview]
Message-ID: <87y1b595y0.ffs@tglx> (raw)
In-Reply-To: <098670097a6fd59f3e254c5294882f3fa12e3c65.camel@gmail.com>
On Tue, Feb 27 2024 at 22:08, mikhail.v.gavrilov@gmail.com wrote:
> On Mon, 2024-02-26 at 19:09 +0100, Thomas Gleixner wrote:
>> we don't have any information about the overall workload,
>
> During measurements nothing was running except iperf3
Ok.
> I don't know how else to help you. What information to provide.
If we want to understand why CPU0 is problematic, then you need to use
tracing to capture what's going on on CPU0 vs. other CPUs.
> About repeatability my "unlucky" scenario.
> I have two MSI MPG B650I EDGE WIFI motherboards and this problem
> happened both at the same time.
Sure. The probe order and the number of interrupts are probably exactly
the same. As the spreading algorithm is very basic, it will result in
exactly the same setup for both.
> It seems the problem has always been there, we just never noticed it.
Exactly.
Thanks,
tglx
next prev parent reply other threads:[~2024-02-27 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABXGCsNnUfCCYVSb_-j-a-cAdONu1r6Fe8p2OtQ5op_wskOfpw@mail.gmail.com>
[not found] ` <43a769dd-aa09-4da3-a226-ecef98f32e0f@infradead.org>
2024-02-03 1:16 ` 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 Randy Dunlap
2024-02-03 2:32 ` Jakub Kicinski
[not found] ` <Zb6D/5R8nNrxveAP@cae.in-ulm.de>
[not found] ` <Zb/30qOGYAH4j6Mn@cae.in-ulm.de>
[not found] ` <CABXGCsPu73D+JS9dpvzX78RktK2VOv_xT8vvuVaQ=B6zs2dMNQ@mail.gmail.com>
[not found] ` <e7b96819-edf7-1f9f-7b01-e2e805c99b33@linux.intel.com>
[not found] ` <CABXGCsPjW_Gr4fGBzYSkr_4tsn0fvuT72G-YJYXcb1a4kX=CQw@mail.gmail.com>
[not found] ` <2d87509a-1515-520c-4b9e-bba4cd4fa2c6@linux.intel.com>
[not found] ` <CABXGCsPdXqRG6v97KDGy+o59xc3ayaq3rLj267veC7YcKVp8ww@mail.gmail.com>
[not found] ` <1126ed0a-bfc1-a752-1b5e-f1339d7a8aa5@linux.intel.com>
[not found] ` <CABXGCsN5_O3iKDOyYxtsGTGDA6fw4962CjzXLSnOK3rscELq+Q@mail.gmail.com>
[not found] ` <a026ecd8-6fba-017d-d673-0d0759a37ed8@linux.intel.com>
[not found] ` <CABXGCsOgy8H4GGcNU1jRE+SzRqwnPeNuy_3xBukjwB-bPxeZrQ@mail.gmail.com>
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 [this message]
2024-02-27 18:03 ` mikhail.v.gavrilov
2024-02-29 9:41 ` Mikhail Gavrilov
2024-03-04 14:10 ` Linux regression tracking (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=87y1b595y0.ffs@tglx \
--to=tglx@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lk@c--e.de \
--cc=mathias.nyman@linux.intel.com \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=niklas.neronin@linux.intel.com \
--cc=rdunlap@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=x86@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).