From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Samuel Dobron <sdobron@redhat.com>,
Daniel Borkmann <daniel@iogearbox.net>,
hawk@kernel.org
Cc: Sebastiano Miano <mianosebastiano@gmail.com>,
bpf@vger.kernel.org, netdev@vger.kernel.org, saeedm@nvidia.com,
tariqt@nvidia.com, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Subject: Re: XDP Performance Regression in recent kernel versions
Date: Mon, 24 Jun 2024 13:46:33 +0200 [thread overview]
Message-ID: <87ed8mftra.fsf@toke.dk> (raw)
In-Reply-To: <CA+h3auMq5vnoyRLvJainG-AFA6f=ivRmu6RjKU4cBv_go975tw@mail.gmail.com>
Samuel Dobron <sdobron@redhat.com> writes:
>> 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?
I don't think we have a formal reporting procedure, but I was planning
to send this to the list, referencing the Bugzilla entry. Seems I
dropped the ball on that; sorry! :(
Can we set up a better reporting procedure for this going forward? A
mailing list, or just a name we can put in reports? Or something else?
Tariq, any preferences?
-Toke
next prev parent reply other threads:[~2024-06-24 11:46 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 [this message]
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
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=87ed8mftra.fsf@toke.dk \
--to=toke@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--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=tariqt@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.