From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, "Morten Brørup" <mb@smartsharesystems.com>,
"David Marchand" <david.marchand@redhat.com>,
"Luca Boccassi" <bluca@debian.org>,
"Kevin Traynor" <ktraynor@redhat.com>
Subject: Re: [PATCH v2] doc: update kernel version requirement
Date: Mon, 21 Jul 2025 19:39:03 +0200 [thread overview]
Message-ID: <6697631.K2JlShyGXD@thomas> (raw)
In-Reply-To: <8fc75987-9397-4290-8c22-d4c6354e2fd2@redhat.com>
21/07/2025 12:45, Kevin Traynor:
> On 10/04/2025 16:20, Stephen Hemminger wrote:
> > The 4.19 kernel version was end of life in December 2024.
> > Update to 5.4 and also add better description of what "not supported"
> > means in this case.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > Acked-by: Morten Brørup <mb@smartsharesystems.com>
> > ---
> > v2 - better wording
> >
> > doc/guides/linux_gsg/sys_reqs.rst | 19 ++++++++++++++-----
> > 1 file changed, 14 insertions(+), 5 deletions(-)
> >
> > diff --git a/doc/guides/linux_gsg/sys_reqs.rst b/doc/guides/linux_gsg/sys_reqs.rst
> > index 5a7d9e4a43..ba48b8afc0 100644
> > --- a/doc/guides/linux_gsg/sys_reqs.rst
> > +++ b/doc/guides/linux_gsg/sys_reqs.rst
> > @@ -105,11 +105,20 @@ System Software
> >
> > **Required:**
> >
> > -* Kernel version >= 4.19
> > -
> > - The kernel version required is based on the oldest long term stable kernel available
> > - at kernel.org when the DPDK version is in development.
> > - Compatibility for recent distribution kernels will be kept, notably RHEL/CentOS 7.
> > +* Kernel version >= 5.4
> > +
> > + The Linux userspace API is compatible across releases but there are some
> > + restrictions. The oldest kernel tested by the DPDK testing infrastructure
> > + is the oldest maintained Long Term Stable (LTS) at time of release.
> > + The DPDK is likely to still work with older releases but it is not guaranteed.
>
> It's just word semantics, but I mentioned before, I don't like the use
> of "guarantee" that is is implied for newer kernels.
>
> We can simply say that older kernels are not tested with and/or that
> DPDK is not maintained to keep compatibility with them etc.
>
> > + Compatibility for recent distribution kernels will be kept, notably RHEL, and Ubuntu.
> > + It may work on older distributions, that are no longer under standard period
> > + but this is no longer but this is no longer tested or guaranteed to work.
>
> "but this is no longer" is repeated
>
> Again, it is implying there are "guarantees" for newer kernels
>
> > + The following are outside the current support window: RHEL 7, SLES 15.5, Ubuntu 20.04
> > + and earlier.
> > +
> > + Some drivers and hardware support may require more recent kernels, check the
> > + documentation (e.g. :doc:`../nics/index`)
> >
> > The kernel version in use can be checked using the command::
> >
>
> With some minor tweaks,
> Acked-by: Kevin Traynor <ktraynor@redhat.com>
>
>
Keeping only the non-controversial parts, not mentioning any distro or version:
* Kernel version >= 5.4
The Linux userspace API is compatible across releases
but there are some restrictions.
The oldest kernel tested by the DPDK testing infrastructure
is the oldest maintained Long Term Stable (LTS) at time of release.
Some drivers and hardware support may require more recent kernels,
check the documentation.
Applied as minimal change.
prev parent reply other threads:[~2025-07-21 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 3:50 [PATCH] " Stephen Hemminger
2025-04-10 15:20 ` [PATCH v2] " Stephen Hemminger
2025-07-21 10:45 ` Kevin Traynor
2025-07-21 17:39 ` Thomas Monjalon [this message]
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=6697631.K2JlShyGXD@thomas \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=mb@smartsharesystems.com \
--cc=stephen@networkplumber.org \
/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).