DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "David Marchand" <david.marchand@redhat.com>,
	"Yang, Qiming" <qiming.yang@intel.com>
Cc: "Tyler Retzlaff" <roretzla@linux.microsoft.com>,
	"Wu, Wenjun1" <wenjun1.wu@intel.com>, <dev@dpdk.org>
Subject: RE: [Bug 1249] [dpdk-23.07] ixgbe port stop failed after launch testpmd
Date: Wed, 14 Jun 2023 09:18:26 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D879CB@smartserver.smartshare.dk> (raw)
In-Reply-To: <CAJFAV8z28VH+tsrOwp8+uAADMnFsyc2C3TPcbSSWesL11WV2OQ@mail.gmail.com>

> From: David Marchand [mailto:david.marchand@redhat.com]
> Sent: Wednesday, 14 June 2023 09.14
> 
> On Wed, Jun 14, 2023 at 8:57 AM Yang, Qiming <qiming.yang@intel.com> wrote:
> >
> > Hi, Tyler
> > May I know why you need to change the legacy atomics? rte_atomic32_xxx
> series action is performance optimized, I don't think the change is needed as
> no bug or other requirement.
> 
> The deprecation of rte_atomic32_xxx atomics is not a new topic.

It would be nice if the roadmap web page mentioned that the legacy rte_atomicXX API is being phased out in favor of C11 atomics, and other long term directions for DPDK.

> 
> Performance impact is not a problem for control path code, is it?
> 
> 
> --
> David Marchand


      reply	other threads:[~2023-06-14  7:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12  7:29 bugzilla
2023-06-12  7:43 ` David Marchand
2023-06-12 16:32   ` Tyler Retzlaff
2023-06-13  9:50     ` David Marchand
2023-06-14  6:57       ` Yang, Qiming
2023-06-14  7:13         ` David Marchand
2023-06-14  7:18           ` Morten Brørup [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=98CBD80474FA8B44BF855DF32C47DC35D879CB@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=qiming.yang@intel.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=wenjun1.wu@intel.com \
    /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).