DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"Gao, DaxueX" <daxuex.gao@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>
Cc: "Morten Brørup" <mb@smartsharesystems.com>,
	"Aaron Conole" <aconole@redhat.com>,
	dev@dpdk.org
Subject: Re: [PATCH] doc: update minimum Linux kernel version
Date: Sat, 17 Feb 2024 14:48:37 -0500	[thread overview]
Message-ID: <CAJvnSUC7qYunYwWBqoPpynfmMy+VzAiitzi7sf4dXtoXjsmtmQ@mail.gmail.com> (raw)
In-Reply-To: <20240216094252.0d3505fa@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]

+Gao, DaxueX <daxuex.gao@intel.com> +Mcnamara, John
<john.mcnamara@intel.com>

Hello,

As you say the Community Lab dropped main and next-* testing for RHEL7 when
the requirement for a C11 compliant compiler was added last year, so we
should already be good to go. We don't have any centos7 testing (centos8
was the first centos introduced for testing at the Community Lab).

Adding Daxue and John so they are aware the Intel Lab will want to
(probably) drop the centos7 testing by 24.07.

Thanks!

On Fri, Feb 16, 2024 at 12:42 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:

> On Fri, 16 Feb 2024 09:29:47 +0100
> Morten Brørup <mb@smartsharesystems.com> wrote:
>
> > The system requirements in the Getting Started Guide [1] says:
> >
> > Kernel version >= 4.14
> > The kernel version required is based on the oldest long term stable
> kernel available at kernel.org when the DPDK version is in development.
> > Compatibility for recent distribution kernels will be kept, notably
> RHEL/CentOS 7.
> >
> > [1]: https://doc.dpdk.org/guides/linux_gsg/sys_reqs.html#system-software
> >
> > If we consider it API breakage to change that, we have to wait until the
> 24.11 release.
> > For future DPDK LTS releases, we should be more careful about what we
> claim to support. And again: If we claim to support something, people
> expect it to be tested in CI.
> >
> > Disregarding the API breakage by stopping support for a system we claim
> to support... RHEL7 testing was changed to LTS only [2], that should
> probably have been applied to CentOS 7 too.
> >
> > [2]:
> https://inbox.dpdk.org/dev/CAJvnSUBcq3gznQD4k=krQ+gu2OxTxA2YJBc=J=LtidFXqgg_hg@mail.gmail.com/
> >
>
> This patch is too late for 24.03 release, by the time the next one happens,
> we can drop CentOS 7 as well as the old kernel.
>

[-- Attachment #2: Type: text/html, Size: 2917 bytes --]

      reply	other threads:[~2024-02-17 19:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-10 16:57 Stephen Hemminger
2024-01-11  9:18 ` Morten Brørup
2024-01-11 18:48   ` Aaron Conole
2024-01-11 19:02   ` Patrick Robb
2024-01-11 19:26     ` Morten Brørup
2024-01-11 19:50       ` Patrick Robb
2024-01-11 19:54       ` Stephen Hemminger
2024-01-11 22:38         ` Morten Brørup
2024-02-16  3:05           ` Stephen Hemminger
2024-02-16  8:29             ` Morten Brørup
2024-02-16 17:22               ` Stephen Hemminger
2024-02-16 17:42               ` Stephen Hemminger
2024-02-17 19:48                 ` Patrick Robb [this message]

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=CAJvnSUC7qYunYwWBqoPpynfmMy+VzAiitzi7sf4dXtoXjsmtmQ@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=aconole@redhat.com \
    --cc=daxuex.gao@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=mb@smartsharesystems.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).