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

From: mikhail . v . gavrilov
Date: Tue Feb 27 2024 - 13:10:45 EST

Next message: Miguel Ojeda: "Re: [PATCH v2 2/3] scripts: generate_rust_target: enable building on RISC-V"
Previous message: Catalin Marinas: "Re: [PATCH bpf-next v3 1/2] arm64: stacktrace: Implement arch_bpf_stack_walk() for the BPF JIT"
In reply to: Thomas Gleixner: "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"
Next in thread: Mikhail Gavrilov: "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"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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.

Attachment: capture-CPU0.zip
Description: Zip archive

Attachment: capture_CPU23.zip
Description: Zip archive