From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Bruce Richardson" <bruce.richardson@intel.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>,
<maxime.coquelin@redhat.com>
Subject: RE: Clarification on Minimum Supported Kernel Version for DPDK
Date: Fri, 21 Mar 2025 11:42:36 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9FB38@smartserver.smartshare.dk> (raw)
In-Reply-To: <Z90kpNrf8HjicUkI@bricha3-mobl1.ger.corp.intel.com>
> From: Bruce Richardson [mailto:bruce.richardson@intel.com]
>
> 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).
I agree regarding distros.
However, embedded systems may be stuck on ancient kernel versions for a variety of reasons.
Documenting the explicit requirements to the kernel are relevant for these.
I would expect all of the DPDK's EAL to behave as expected, so this should be the basis for defining DPDK's minimum kernel requirements - regarding both kernel version and optional kernel features required.
<noise>
In this context, "all of the EAL" really should mean the core of the EAL, exclusive the non-optional bloat that has nothing to do with abstracting the HW and O/S, and thus shouldn't be part of the EAL. But for now, I think we need to consider the EAL as-is, incl. any bloat.
</noise>
Some DPDK drivers may have additional kernel requirements.
Any such requirements should be documented with the individual drivers.
And, preferably, any driver should be able to degrade its capabilities gracefully when some optional requirements are not fulfilled.
In other words: We don't want DPDK's minimum kernel requirements to depend on some driver requiring some new and shiny kernel feature - the minimum kernel requirements should only depend on the EAL.
And - going back to the original question, triggering this discussion - we need to settle on a minimum kernel version for the CI testing at UNH.
next prev parent reply other threads:[~2025-03-21 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMEVEZvCoVpMjFpmY29-x0zB2tQvNrJsTacs6-Zzx4jJB_GsoQ@mail.gmail.com>
2025-03-21 6:28 ` Morten Brørup
2025-03-21 8:34 ` Bruce Richardson
2025-03-21 10:42 ` Morten Brørup [this message]
2025-03-21 15:52 ` Stephen Hemminger
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=98CBD80474FA8B44BF855DF32C47DC35E9FB38@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=alialnu@nvidia.com \
--cc=bruce.richardson@intel.com \
--cc=ccheng@iol.unh.edu \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=galco@nvidia.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).