From: Tariq Toukan <tariqt@nvidia.com>
To: Samuel Dobron <sdobron@redhat.com>,
Daniel Borkmann <daniel@iogearbox.net>,
hawk@kernel.org, Dragos Tatulea <dtatulea@nvidia.com>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"Sebastiano Miano" <mianosebastiano@gmail.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org, saeedm@nvidia.com,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: XDP Performance Regression in recent kernel versions
Date: Sun, 30 Jun 2024 14:43:34 +0300 [thread overview]
Message-ID: <c97e0085-be67-415c-ae06-7ef38992fab1@nvidia.com> (raw)
In-Reply-To: <CA+h3auMq5vnoyRLvJainG-AFA6f=ivRmu6RjKU4cBv_go975tw@mail.gmail.com>
On 21/06/2024 15:35, Samuel Dobron wrote:
> Hey all,
>
> Yeah, we do tests for ELN kernels [1] on a regular basis. Since
> ~January of this year.
>
> As already mentioned, mlx5 is the only driver affected by this regression.
> Unfortunately, I think Jesper is actually hitting 2 regressions we noticed,
> the one already mentioned by Toke, another one [0] has been reported
> in early February.
> Btw. issue mentioned by Toke has been moved to Jira, see [5].
>
> Not sure all of you are able to see the content of [0], Jira says it's
> RH-confidental.
> So, I am not sure how much I can share without being fired :D. Anyway,
> affected kernels have been released a while ago, so anyone can find it
> on its own.
> Basically, we detected 5% regression on XDP_DROP+mlx5 (currently, we
> don't have data for any other XDP mode) in kernel-5.14 compared to
> previous builds.
>
> From tests history, I can see (most likely) the same improvement
> on 6.10rc2 (from 15Mpps to 17-18Mpps), so I'd say 20% drop has been
> (partially) fixed?
>
> For earlier 6.10. kernels we don't have data due to [3] (there is regression on
> XDP_DROP as well, but I believe it's turbo-boost issue, as I mentioned
> in issue).
> So if you want to run tests on 6.10. please see [3].
>
> Summary XDP_DROP+mlx5@25G:
> kernel pps
> <5.14 20.5M baseline
>> =5.14 19M [0]
> <6.4 19-20M baseline for ELN kernels
>> =6.4 15M [4 and 5] (mentioned by Toke)
+ @Dragos
That's about when we added several changes to the RX datapath.
Most relevant are:
- Fully removing the in-driver RX page-cache.
- Refactoring to support XDP multi-buffer.
We tested XDP performance before submission, I don't recall we noticed
such a degradation.
I'll check with Dragos as he probably has these reports.
>> =6.10 ??? [3]
>> =6.10rc2 17M-18M
>
>
>> It looks like this is known since March, was this ever reported to Nvidia back
>> then? :/
>
> Not sure if that's a question for me, I was told, filling an issue in
> Bugzilla/Jira is where
> our competences end. Who is supposed to report it to them?
>
>> Given XDP is in the critical path for many in production, we should think about
>> regular performance reporting for the different vendors for each released kernel,
>> similar to here [0].
>
> I think this might be the part of upstream kernel testing with LNST?
> Maybe Jesper
> knows more about that? Until then, I think, I can let you know about
> new regressions we catch.
>
> Thanks,
> Sam.
>
> [0] https://issues.redhat.com/browse/RHEL-24054
> [1] https://koji.fedoraproject.org/koji/search?terms=kernel-%5Cd.*eln*&type=build&match=regexp
> [2] https://koji.fedoraproject.org/koji/buildinfo?buildID=2469107
> [3] https://bugzilla.redhat.com/show_bug.cgi?id=2282969
> [4] https://bugzilla.redhat.com/show_bug.cgi?id=2270408
> [5] https://issues.redhat.com/browse/RHEL-24054
>
next prev parent reply other threads:[~2024-06-30 11:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 15:28 XDP Performance Regression in recent kernel versions Sebastiano Miano
2024-06-19 6:00 ` Tariq Toukan
2024-06-19 15:17 ` Sebastiano Miano
2024-06-19 16:27 ` Jesper Dangaard Brouer
2024-06-19 19:17 ` Toke Høiland-Jørgensen
2024-06-20 9:52 ` Daniel Borkmann
2024-06-21 12:35 ` Samuel Dobron
2024-06-24 11:46 ` Toke Høiland-Jørgensen
2024-06-30 10:25 ` Tariq Toukan
2024-07-22 10:57 ` Samuel Dobron
2024-06-30 11:43 ` Tariq Toukan [this message]
2024-07-22 9:26 ` Dragos Tatulea
2024-07-23 9:52 ` Carolina Jubran
2024-07-24 15:36 ` Toke Høiland-Jørgensen
2024-07-25 12:27 ` Samuel Dobron
2024-07-26 8:09 ` Dragos Tatulea
2024-07-29 18:00 ` Samuel Dobron
2024-07-30 11:04 ` Samuel Dobron
2024-12-11 13:20 ` Samuel Dobron
2025-01-08 9:26 ` Carolina Jubran
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=c97e0085-be67-415c-ae06-7ef38992fab1@nvidia.com \
--to=tariqt@nvidia.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=kuba@kernel.org \
--cc=mianosebastiano@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=sdobron@redhat.com \
--cc=toke@redhat.com \
/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