From: Stephen Hemminger <stephen@networkplumber.org>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: <dev@dpdk.org>
Subject: Re: Linux kernel version for DPDK 24.11
Date: Tue, 13 Aug 2024 14:13:33 -0700 [thread overview]
Message-ID: <20240813141333.23541e4b@hermes.local> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9F626@smartserver.smartshare.dk>
On Tue, 13 Aug 2024 22:53:55 +0200
Morten Brørup <mb@smartsharesystems.com> wrote:
> Stephen,
>
> Kernel 4.19 will reach EOL in December 2024 [1], so we should skip ahead to 5.4 (projected EOL December 2025) or 5.10 (projected EOL December 2026).
>
> For reference, the CIP project provides a SLTS (Super Long-Time Stable) kernel based on version 5.10 [2]. Their previous SLTS was based on kernel version 4.19.
>
> Based on the above information, it could make sense updating the DPDK minimum requirements for DPDK 24.11 to kernel version 5.10.
>
> You usually have a good overview of what is going on in the relevant distros. Could you please provide a doc patch like you have done before [3].
>
> [1]: https://www.kernel.org/category/releases.html
> [2]: https://www.cip-project.org/blog/2022/04/04/cip-expands-work-on-slts-kernel-maintenance
> [3]: https://git.dpdk.org/dpdk/commit/doc/guides/linux_gsg?id=0b9db7caa8c223a541a323793068bc920789331c
>
>
> Med venlig hilsen / Kind regards,
> -Morten Brørup
>
Yes, but we still have to support the distro's (Ubuntu, Fedora, RHEL) which may have older kernels.
Kernel version doesn't matter as much now that drivers are gone. But the issue is more about
potentially missing stuff in header files.
next prev parent reply other threads:[~2024-08-13 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 20:53 Morten Brørup
2024-08-13 21:13 ` Stephen Hemminger [this message]
2024-08-13 21:43 ` Morten Brørup
2024-08-14 10:23 ` Bruce Richardson
2024-08-13 21:16 ` 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=20240813141333.23541e4b@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.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;
as well as URLs for NNTP newsgroup(s).