DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH] doc: update oldest supported kernel
Date: Tue, 26 Sep 2017 08:17:12 +0100	[thread overview]
Message-ID: <20170926071712.25009-1-stephen@networkplumber.org> (raw)

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>
---
 doc/guides/linux_gsg/sys_reqs.rst | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/doc/guides/linux_gsg/sys_reqs.rst b/doc/guides/linux_gsg/sys_reqs.rst
index eb8442c62226..b335da2c086d 100644
--- a/doc/guides/linux_gsg/sys_reqs.rst
+++ b/doc/guides/linux_gsg/sys_reqs.rst
@@ -121,8 +121,10 @@ System Software
 
 **Required:**
 
-*   Kernel version >= 2.6.34
+*   Kernel version >= 3.2.93
 
+    The kernel version required is based on the oldest long term stable kernel available
+    at kernel.org when the DPDK version is released.
     The kernel version in use can be checked using the command::
 
         uname -r
-- 
2.11.0

             reply	other threads:[~2017-09-26  7:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-26  7:17 Stephen Hemminger [this message]
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 ` [dpdk-dev] [PATCH v2] doc: update oldest supported kernel in Linux guide Thomas Monjalon
2017-12-12 14:20   ` 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=20170926071712.25009-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.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).