From: Samuel Dobron <sdobron@redhat.com>
To: Carolina Jubran <cjubran@nvidia.com>,
Dragos Tatulea <dtatulea@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>,
"daniel@iogearbox.net" <daniel@iogearbox.net>,
"hawk@kernel.org" <hawk@kernel.org>,
"mianosebastiano@gmail.com" <mianosebastiano@gmail.com>
Cc: "toke@redhat.com" <toke@redhat.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
Saeed Mahameed <saeedm@nvidia.com>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: XDP Performance Regression in recent kernel versions
Date: Tue, 30 Jul 2024 13:04:22 +0200 [thread overview]
Message-ID: <03c24731-e56f-44b2-b0a3-6afd7f14f77b@redhat.com> (raw)
In-Reply-To: <b1148fab-ecf3-46c1-9039-597cc80f3d28@nvidia.com>
> Could you try adding the mentioned parameters to your kernel arguments
> and check if you still see the degradation?
Hey,
So i tried multiple kernels around v5.15 as well as couple of previous
v6.xx and there is no difference with spectre v2 mitigations enabled
or disabled.
No difference on other drivers as well.
Sam.
next prev parent reply other threads:[~2024-07-30 11:04 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
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 [this message]
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=03c24731-e56f-44b2-b0a3-6afd7f14f77b@redhat.com \
--to=sdobron@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=cjubran@nvidia.com \
--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=tariqt@nvidia.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