From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "david.marchand@redhat.com" <david.marchand@redhat.com>,
"ktraynor@redhat.com" <ktraynor@redhat.com>,
"maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
"rasland@nvidia.com" <rasland@nvidia.com>,
"Ajit Khaparde (ajit.khaparde@broadcom.com)"
<ajit.khaparde@broadcom.com>,
"aconole@redhat.com" <aconole@redhat.com>,
"bruce.richardson@intel.com" <bruce.richardson@intel.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
"mdr@ashroe.eu" <mdr@ashroe.eu>, nd <nd@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] RHEL 7 support
Date: Mon, 12 Jul 2021 17:34:21 +0000 [thread overview]
Message-ID: <DBAPR08MB581403C7BFFAC43C8311A9B298159@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <2874531.2S3dPSLiCe@thomas>
<snip>
>
> Hi,
>
> I would like to open a discussion about RHEL 7 support in DPDK.
> How long do we want to support it in new DPDK versions?
> Can we drop RHEL 7 support starting DPDK 21.11?
I think the concerns were from Redhat and Intel.
>
> If we decide to drop RHEL 7 support, does it mean we can generally use
> standard C11 atomics?
What is the next RHEL version we support officially?
If we adopt C11 atomic APIs, we need to think about windows support too.
>
> What other benefits or impacts can you think about?
>
next prev parent reply other threads:[~2021-07-12 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-09 18:33 Thomas Monjalon
2021-07-12 17:34 ` Honnappa Nagarahalli [this message]
2021-07-13 9:47 ` Kevin Traynor
2021-07-13 15:49 ` Lance Richardson
2021-07-13 16:15 ` Ajit Khaparde
2021-07-19 16:52 ` Tyler Retzlaff
2022-04-11 8:23 ` Tyler Retzlaff
2022-04-11 9:09 ` Bruce Richardson
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=DBAPR08MB581403C7BFFAC43C8311A9B298159@DBAPR08MB5814.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=aconole@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mdr@ashroe.eu \
--cc=nd@arm.com \
--cc=rasland@nvidia.com \
--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).