From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>, Neil Horman <nhorman@redhat.com>,
"Luca Boccassi" <luca.boccassi@gmail.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH] doc: update oldest supported kernel
Date: Fri, 13 Oct 2017 15:49:07 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23EDD1BD6@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20170926071712.25009-1-stephen@networkplumber.org>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Stephen Hemminger
> Sent: Tuesday, September 26, 2017 8:17 AM
> To: dev@dpdk.org
> Cc: Stephen Hemminger <stephen@networkplumber.org>
> Subject: [dpdk-dev] [PATCH] doc: update oldest supported kernel
>
> 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.
Hi,
OSV people, any objection to this?
John
next prev parent reply other threads:[~2017-10-13 15:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 7:17 Stephen Hemminger
2017-10-13 15:49 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE23EDD1BD6@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=bruce.richardson@intel.com \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=luca.boccassi@gmail.com \
--cc=nhorman@redhat.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).