From: Bruce Richardson <bruce.richardson@intel.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: Cody Cheng <ccheng@iol.unh.edu>,
Kevin Traynor <ktraynor@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>,
<techboard@dpdk.org>,
"Tyler Retzlaff" <roretzla@linux.microsoft.com>,
Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>, <dev@dpdk.org>,
Ali Alnubani <alialnu@nvidia.com>, <galco@nvidia.com>
Subject: Re: Clarification on Minimum Supported Kernel Version for DPDK
Date: Fri, 21 Mar 2025 08:34:44 +0000 [thread overview]
Message-ID: <Z90kpNrf8HjicUkI@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9FB37@smartserver.smartshare.dk>
On Fri, Mar 21, 2025 at 07:28:45AM +0100, Morten Brørup wrote:
> @Kevin, @Stephen, @Bruce,
>
> I cannot reliably answer Cody's question, and it may need further discussion.
>
> What is your opinion on minimum Linux kernel version requirements?
>
> @Thomas: In the future, the DPDK release notes should mention the minimum Linux kernel requirements.
>
Another question is - should we even have a minimum kernel version? Are we
aware of any kernel features beyond vfio-pci driver which DPDK requires to
run? As a userspace application, I think DPDK should just work with
whatever distro-provided kernel is provided (assuming distro is relatively
recent).
/Bruce
next prev parent reply other threads:[~2025-03-21 8:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMEVEZvCoVpMjFpmY29-x0zB2tQvNrJsTacs6-Zzx4jJB_GsoQ@mail.gmail.com>
2025-03-21 6:28 ` Clarification on Minimum Supported Kernel Version for DPDK Morten Brørup
2025-03-21 8:34 ` Bruce Richardson [this message]
2025-03-21 10:42 ` Morten Brørup
2025-03-21 15:52 ` Stephen Hemminger
2025-03-22 13:02 ` Morten Brørup
2025-03-26 14:47 ` Cody Cheng
2025-03-31 18:09 ` Patrick Robb
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=Z90kpNrf8HjicUkI@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=alialnu@nvidia.com \
--cc=ccheng@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=galco@nvidia.com \
--cc=ktraynor@redhat.com \
--cc=mb@smartsharesystems.com \
--cc=roretzla@linux.microsoft.com \
--cc=stephen@networkplumber.org \
--cc=techboard@dpdk.org \
--cc=thomas@monjalon.net \
/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.