DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: CentOs End of Life?
Date: Tue, 30 Jan 2024 09:45:15 -0800	[thread overview]
Message-ID: <20240130094515.08631412@hermes.local> (raw)
In-Reply-To: <Zbky0kzhqoAKTT8V@bricha3-MOBL.ger.corp.intel.com>

On Tue, 30 Jan 2024 17:33:06 +0000
Bruce Richardson <bruce.richardson@intel.com> wrote:

> On Tue, Jan 30, 2024 at 09:18:49AM -0800, Stephen Hemminger wrote:
> > While reworking tap device, one issue is how to keep (or drop) the support
> > of older Enterprise releases. The tap flow support is doing some workarounds
> > to include missing support, but these are not the right way to do it.
> > 
> > The question is: is this even worth keeping?
> > CentOS 7 reaches end of life in June 2024.
> > CentOS 7 is using a kernel which is no longer supported.
> > 
> > If we drop CentOS 7, that means dropping RHEL7 and would need to be hightlighted
> > in the docs.  
> 
> I thought we had already dropped it. Centos 7 doesn't come by default with
> a C11-supporting compiler.
> 
> /Bruce

Well my recent patches were getting hit in CI by:

Meson Build Summary: 24 Builds Done, 23 Successful, 1 Failures, 0 Blocked

+-------------------+------------+--------------+------------+------------+-----------+----------+------------+
| os                | gcc-static | clang-static | icc-static | gcc-shared | gcc-debug | document | gcc-16byte |
+-------------------+------------+--------------+------------+------------+-----------+----------+------------+
| OpenAnolis8.8-64  | pass       |              |            |            |           |          |            |
| FreeBSD13-64      | pass       | pass         |            | pass       | pass      |          |            |
| RHEL92-64         | pass       | pass         |            | pass       | pass      |          |            |
| SUSE15-64         | pass       | pass         |            |            |           |          |            |
| CBL-Mariner2.0-64 | pass       |              |            |            |           |          |            |
| UB2204-32         | pass       |              |            |            |           |          |            |
| RHEL89-64         | pass       |              |            |            |           |          |            |
| UB2204-64         | pass       | pass         |            |            |           | pass     | pass       |
| CentOS79-64       | fail       |              |            |            |           |          |            | <<<<<<< This needs to go
| RHEL92-64Rt       | pass       |              |            |            |           |          |            |
| UB2310-64         | pass       |              |            |            |           |          |            |
| FC39-64           | pass       | pass         |            |            |           |          |            |
| UB2204-64Rt       | pass       |              |            |            |           |          |            |
+-------------------+------------+--------------+------------+------------+-----------+----------+------------+

  reply	other threads:[~2024-01-30 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 17:18 Stephen Hemminger
2024-01-30 17:33 ` Bruce Richardson
2024-01-30 17:45   ` Stephen Hemminger [this message]
2024-01-30 19:10   ` Tyler Retzlaff

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=20240130094515.08631412@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=bruce.richardson@intel.com \
    --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).