From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>, <dev@dpdk.org>
Subject: RE: [RFC] doc: update required kernel version to 4.14
Date: Tue, 2 Aug 2022 18:28:58 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D8722C@smartserver.smartshare.dk> (raw)
In-Reply-To: <20220802153543.7622-1-stephen@networkplumber.org>
> From: Stephen Hemminger [mailto:stephen@networkplumber.org]
> Sent: Tuesday, 2 August 2022 17.36
>
> The 4.4 kernel was end of life in February 2022,
> and the next LTS is 4.9 and it is reaching EOL in January 2023.
> The main distro using 4.9 is Debian Stretch and it is no longer
> supported. When DPDK 22.11 is released, the 4.9 kernel would
> only be receiving fixes for three months; therefore
> lets make the official version 4.14.
Makes very good sense to me.
>
> As always, current major enterprise Linux releases will continue
> to be supported, but those releases don't track regular kernel
> version numbering.
>
> For full details on kernel support see:
> https://www.kernel.org/category/releases.html
> https://en.wikipedia.org/wiki/Linux_kernel_version_history
>
> Debian Stretch:
> https://www.debian.org/releases/stretch/
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
> doc/guides/linux_gsg/sys_reqs.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/guides/linux_gsg/sys_reqs.rst
> b/doc/guides/linux_gsg/sys_reqs.rst
> index 08d45898f025..ed22b6e80b4c 100644
> --- a/doc/guides/linux_gsg/sys_reqs.rst
> +++ b/doc/guides/linux_gsg/sys_reqs.rst
> @@ -105,7 +105,7 @@ System Software
>
> **Required:**
>
> -* Kernel version >= 4.4
> +* Kernel version >= 4.14
>
> The kernel version required is based on the oldest long term
> stable kernel available
> at kernel.org when the DPDK version is in development.
Shouldn't we generalize your reasoning and update this too? It should reflect that we require more than 3 months to projected EOL, e.g. minimum one year.
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-08-02 16:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 16:45 [PATCH 0/2] update DPDK Linux kernel version Stephen Hemminger
2022-02-17 16:45 ` [PATCH 1/2] doc: update required kernel version to 4.9 Stephen Hemminger
2022-05-26 18:23 ` Stephen Hemminger
2022-08-02 15:35 ` [RFC] doc: update required kernel version to 4.14 Stephen Hemminger
2022-08-02 16:28 ` Morten Brørup [this message]
2022-10-31 15:31 ` Thomas Monjalon
2022-02-17 16:45 ` [PATCH 2/2] known_issues: drop note about UIO with really old kernels Stephen Hemminger
2023-07-03 23:59 ` Stephen Hemminger
2023-07-17 14:14 ` Bruce Richardson
2023-11-27 16:42 ` Thomas Monjalon
2022-02-17 16:53 ` [PATCH 0/2] update DPDK Linux kernel version Bruce Richardson
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=98CBD80474FA8B44BF855DF32C47DC35D8722C@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--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).