[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABXGCsOUzbgrTHVDHkepcxK15HBRXYLq2S0ohkCXRF347fUuJA@mail.gmail.com>
Date: Thu, 29 Feb 2024 14:41:16 +0500
From: Mikhail Gavrilov <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, Feb 27, 2024 at 11:03 PM <mikhail.v.gavrilov@...il.com> wrote:
>
> 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.
>
Sorry for the noise.
Because I am unsure whether you received or not my previous message
with captures.
I upload them to the mega file exchange server and share links below.
capture CPU0: https://mega.nz/file/Ik5XiZAS#Hra7Xtzplp8xcHYFj4JXnpp8T-0UA0nhNSIJJLEcSBk
capture CPU23: https://mega.nz/file/swg0CQ4C#PvGv_WXmtnATD7tNun5xz-lfA5GGqA-KOv1ZbVRJ_lI
--
Best Regards,
Mike Gavrilov.
Powered by blists - more mailing lists