From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: stephen@networkplumber.org, bluca@debian.org
Subject: [dpdk-dev] [PATCH v2] doc: update oldest supported kernel in Linux guide
Date: Tue, 28 Nov 2017 23:02:22 +0100 [thread overview]
Message-ID: <20171128220222.14783-1-thomas@monjalon.net> (raw)
In-Reply-To: <20170926071712.25009-1-stephen@networkplumber.org>
From: Stephen Hemminger <stephen@networkplumber.org>
The DPDK needs to stay up to date with current LTS Linux kernel support.
If the kernel is older than LTS it is likely to be insecure and buggy.
Therefore only require DPDK to work on oldest LTS kernel.
If distribution vendors want to support DPDK on older kernels, that is
their choice. But the upstream source does not need to be cluttered
with support for this.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
doc/guides/linux_gsg/sys_reqs.rst | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/doc/guides/linux_gsg/sys_reqs.rst b/doc/guides/linux_gsg/sys_reqs.rst
index 3e7fe6373..5ff740fc4 100644
--- a/doc/guides/linux_gsg/sys_reqs.rst
+++ b/doc/guides/linux_gsg/sys_reqs.rst
@@ -121,7 +121,10 @@ System Software
**Required:**
-* Kernel version >= 2.6.34
+* Kernel version >= 3.2
+
+ The kernel version required is based on the oldest long term stable kernel available
+ at kernel.org when the DPDK version is in development.
The kernel version in use can be checked using the command::
--
2.15.0
next prev parent reply other threads:[~2017-11-28 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 7:17 [dpdk-dev] [PATCH] doc: update oldest supported kernel Stephen Hemminger
2017-10-13 15:49 ` Mcnamara, John
2017-10-13 15:55 ` Luca Boccassi
2017-10-13 15:54 ` Luca Boccassi
2017-11-12 4:30 ` Thomas Monjalon
2017-11-15 15:55 ` Ferruh Yigit
2017-11-28 22:02 ` Thomas Monjalon [this message]
2017-12-12 14:20 ` [dpdk-dev] [PATCH v2] doc: update oldest supported kernel in Linux guide Kovacevic, Marko
2017-12-15 14:24 ` Thomas Monjalon
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=20171128220222.14783-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=bluca@debian.org \
--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).