From: Luca Boccassi <bluca@debian.org>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [PATCH] doc: add kernel version deprecation notice
Date: Wed, 14 Feb 2018 10:54:44 +0000 [thread overview]
Message-ID: <1518605684.4059.16.camel@debian.org> (raw)
In-Reply-To: <470fdbc6-7280-1523-da8b-91fda8fafbcf@redhat.com>
On Wed, 2018-02-14 at 11:38 +0100, Maxime Coquelin wrote:
>
> On 02/14/2018 11:31 AM, Luca Boccassi wrote:
> > On Wed, 2018-02-14 at 00:58 +0100, Thomas Monjalon wrote:
> > > 31/01/2018 16:27, Stephen Hemminger:
> > > > Notify users of upcoming change in kernel requirement.
> > > > Encourage users to use current LTS kernel version.
> > > >
> > > > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > > > ---
> > > > +* linux: Linux kernel version 3.2 (which is the current
> > > > minimum
> > > > required
> > > > + version for the DPDK) will be end of life in May 2018.
> > > > Therefore
> > > > the planned
> > > > + minimum required kernel version for DPDK 18.5 will be next
> > > > oldest Long
> > > > + Term Stable (LTS) version which is 3.10. The recommended
> > > > kernel
> > > > version is
> > > > + the latest LTS kernel which currently is 4.14.
> > >
> > > We could print a warning at EAL init if kernel version does not
> > > satisfy the
> > > minimal requirement.
> > >
> > > Acked-by: Thomas Monjalon <thomas@monjalon.net>
> >
> > Note that 3.10 is dead as well since last year (as I discovered
> > with
> > immense joy when I had to backport meltdown fixes...), the next LTS
> > in
> > 3.16 which will be maintained until 04/2020.
> >
>
> In this case we should differentiate upstream Kernel versions from
> downstream ones. For example, RHEL7/CentOS7 are based on v3.10 ans
> still
> maintained.
Ubuntu does 3.13 as well - I think the problem is that if we want to
support distro-specific LTS kernel versions, we need volunteers to do
the work for them :-)
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-02-14 10:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 15:27 [PATCH] doc: add kernel version deprecation notice Stephen Hemminger
2018-02-13 23:58 ` Thomas Monjalon
2018-02-14 10:26 ` Olivier Matz
2018-02-14 10:31 ` Luca Boccassi
2018-02-14 10:38 ` Thomas Monjalon
2018-02-14 10:38 ` Maxime Coquelin
2018-02-14 10:54 ` Luca Boccassi [this message]
2018-02-14 11:44 ` Bruce Richardson
2018-02-14 18:08 ` Stephen Hemminger
2018-02-15 9:26 ` Bruce Richardson
2018-02-15 14:15 ` Aaron Conole
2018-05-24 20:53 ` Thomas Monjalon
2018-02-14 10:33 ` Maxime Coquelin
2018-11-24 18:44 ` [PATCH v2] doc: announce Linux support change 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=1518605684.4059.16.camel@debian.org \
--to=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.