[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <960fd112b294a902e1bea1fdd8e04a708a05cf45.camel@gmail.com>
Date: Tue, 27 Feb 2024 23:03:45 +0500
From: mikhail.v.gavrilov@...il.com
To: Thomas Gleixner <tglx@...utronix.de>, Mathias Nyman
<mathias.nyman@...ux.intel.com>, Linux regressions mailing list
<regressions@...ts.linux.dev>
Cc: "Christian A. Ehrhardt" <lk@...e.de>, niklas.neronin@...ux.intel.com,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>, Greg KH
<gregkh@...uxfoundation.org>, linux-usb@...r.kernel.org, x86@...nel.org,
netdev@...r.kernel.org, Randy Dunlap <rdunlap@...radead.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
On Tue, 2024-02-27 at 18:23 +0100, Thomas Gleixner wrote:
> 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.
I am not hear what kind of profiler software you prefer.
I famous with sysprof and attach here captures for both cases CPU0 vs
CPU23. I hope this helps clear things up.
Thanks!
--
Best Regards,
Mike Gavrilov.
Download attachment "capture-CPU0.zip" of type "application/zip" (3585466 bytes)
Download attachment "capture_CPU23.zip" of type "application/zip" (3576676 bytes)
Powered by blists - more mailing lists