DPDK patches and discussions
 help / color / mirror / Atom feed
From: Aaron Conole <aconole@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Luca Boccassi <bluca@debian.org>,
	Maxime Coquelin <maxime.coquelin@redhat.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Kevin Traynor <ktraynor@redhat.com>,
	dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] doc: add kernel version deprecation notice
Date: Thu, 15 Feb 2018 09:15:55 -0500	[thread overview]
Message-ID: <f7tfu625of8.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <20180215092559.GA11448@bricha3-MOBL3.ger.corp.intel.com> (Bruce Richardson's message of "Thu, 15 Feb 2018 09:26:00 +0000")

Bruce Richardson <bruce.richardson@intel.com> writes:

> On Wed, Feb 14, 2018 at 10:08:34AM -0800, Stephen Hemminger wrote:
>> On Wed, 14 Feb 2018 11:44:15 +0000
>> Bruce Richardson <bruce.richardson@intel.com> wrote:
>> 
>> > On Wed, Feb 14, 2018 at 10:54:44AM +0000, Luca Boccassi wrote:
>> > > 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 :-)
>> > > 
>> > > --   
>> > I think our kernel support plans need to be two-fold:
>> > 
>> > 1) we need to support a minimum "kernel.org" kernel version, which is
>> > what the deprecation notice is about.
>> > 2) we also will be supporting LTS distributions, e.g. I would expect us to
>> > always support the latest RHEL, so that should be noted explicitly in the
>> > GSG IMHO.
>> 
>> For distributions, we need to have a maintainer. Ideally, from the vendor or
>> project doing the distribution.
>
> I actually don't think that's really necessary. It's very rare for
> changes to LTS distributions to cause us problems, it's far more common
> to have issues the other way round. Because of that, it's working fine
> just refusing to apply patches that break the build on our supported
> distributions.

I tend to agree with Bruce.  What is specifically being requested?  From
a downstream perspective, we ship dpdk and applications enabled with
dpdk.

We support those applications, and that version of the library
(including performing bugfixes, etc).  In addition, we do our best to
support upstream efforts (eg. working with vendors, working with
applications, working with users, contributing bug fixes, etc).

Is there something different that needs to happen?  Happy to help - just
need to know what helping means :)

  reply	other threads:[~2018-02-15 14:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 15:27 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
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 [this message]
2018-05-24 20:53           ` Thomas Monjalon
2018-02-14 10:33 ` Maxime Coquelin
2018-11-24 18:44 ` [dpdk-dev] [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=f7tfu625of8.fsf@dhcp-25.97.bos.redhat.com \
    --to=aconole@redhat.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ktraynor@redhat.com \
    --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 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).