All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>,
	David Hunt <david.hunt@intel.com>,
	Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	Jerin Jacob <jerinj@marvell.com>,
	Konstantin Ananyev <konstantin.v.ananyev@yandex.ru>,
	Sameh Gobriel <sameh.gobriel@intel.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	Vladimir Medvedkin <vladimir.medvedkin@intel.com>,
	Yipeng Wang <yipeng1.wang@intel.com>,
	mb@smartsharesystems.com, thomas@monjalon.net,
	Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: [PATCH v2 0/6] use rte atomic thread fence
Date: Wed, 14 Feb 2024 22:50:53 -0800	[thread overview]
Message-ID: <1707979859-3984-1-git-send-email-roretzla@linux.microsoft.com> (raw)
In-Reply-To: <1698894265-22963-1-git-send-email-roretzla@linux.microsoft.com>

Replace use of __atomic_thread_fence with rte_atomic_thread_fence.

Notes:

  The rest of lib/lpm will be converted to rte_atomic in a separate
  series (to be submitted soon).

  There are existing checkpatches checks that catch use of both
  __atomic_thread_fence and __rte_atomic_thread_fence in new
  submissions.

v2:
    * change series to use rte_atomic_thread_fence instead of
      __rte_atomic_thread_fence (internal)
    * also change __atomic_thread_fence in lib/lpm

Tyler Retzlaff (6):
  distributor: use rte atomic thread fence
  eal: use rte atomic thread fence
  hash: use rte atomic thread fence
  ring: use rte atomic thread fence
  stack: use rte atomic thread fence
  lpm: use rte atomic thread fence

 lib/distributor/rte_distributor.c |  2 +-
 lib/eal/common/eal_common_trace.c |  2 +-
 lib/eal/include/rte_mcslock.h     |  4 ++--
 lib/hash/rte_cuckoo_hash.c        | 10 +++++-----
 lib/lpm/rte_lpm.c                 |  4 ++--
 lib/ring/rte_ring_c11_pvt.h       |  4 ++--
 lib/stack/rte_stack_lf_c11.h      |  2 +-
 7 files changed, 14 insertions(+), 14 deletions(-)

-- 
1.8.3.1


  parent reply	other threads:[~2024-02-15  6:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02  3:04 [PATCH 0/5] use rte atomic thread fence Tyler Retzlaff
2023-11-02  3:04 ` [PATCH 1/5] distributor: " Tyler Retzlaff
2023-11-02  3:04 ` [PATCH 2/5] eal: " Tyler Retzlaff
2023-11-02  3:04 ` [PATCH 3/5] hash: " Tyler Retzlaff
2023-11-02  3:04 ` [PATCH 4/5] ring: " Tyler Retzlaff
2023-11-02  3:04 ` [PATCH 5/5] stack: " Tyler Retzlaff
2023-11-02  7:42 ` [PATCH 0/5] " Morten Brørup
2023-11-08 17:04 ` Thomas Monjalon
2023-11-08 18:49   ` Tyler Retzlaff
2024-02-14 22:40     ` Thomas Monjalon
2024-02-15  6:50 ` Tyler Retzlaff [this message]
2024-02-15  6:50   ` [PATCH v2 1/6] distributor: " Tyler Retzlaff
2024-02-15  6:50   ` [PATCH v2 2/6] eal: " Tyler Retzlaff
2024-02-15  6:50   ` [PATCH v2 3/6] hash: " Tyler Retzlaff
2024-02-15  6:50   ` [PATCH v2 4/6] ring: " Tyler Retzlaff
2024-02-15  6:50   ` [PATCH v2 5/6] stack: " Tyler Retzlaff
2024-02-15  6:50   ` [PATCH v2 6/6] lpm: " Tyler Retzlaff
2024-02-18  3:23   ` [PATCH v2 0/6] " fengchengwen
2024-02-18 12:18     ` 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=1707979859-3984-1-git-send-email-roretzla@linux.microsoft.com \
    --to=roretzla@linux.microsoft.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jerinj@marvell.com \
    --cc=konstantin.v.ananyev@yandex.ru \
    --cc=mb@smartsharesystems.com \
    --cc=sameh.gobriel@intel.com \
    --cc=skori@marvell.com \
    --cc=thomas@monjalon.net \
    --cc=vladimir.medvedkin@intel.com \
    --cc=yipeng1.wang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.