DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Konstantin Ananyev <konstantin.ananyev@intel.com>
Cc: dev@dpdk.org, jerin.jacob@caviumnetworks.com
Subject: Re: [dpdk-dev] [PATCH v3 1/2] test/test: introduce new test-case for rte_smp_mb()
Date: Tue, 16 Jan 2018 01:16:38 +0100	[thread overview]
Message-ID: <1920273.q5HlxWAJJN@xps> (raw)
In-Reply-To: <1516028680-2342-2-git-send-email-konstantin.ananyev@intel.com>

15/01/2018 16:04, Konstantin Ananyev:
> Simple functional test for rte_smp_mb() implementations.
> Also when executed on a single lcore could be used as rough
> estimation how many cycles particular implementation of rte_smp_mb()
> might take.
> 
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> ---
>  test/test/Makefile       |   1 +
>  test/test/test_barrier.c | 286 +++++++++++++++++++++++++++++++++++++++++++++++

I will add
	F: test/test/test_barrier.c
in MAINTAINERS, when applying.

> +static inline void
> +store_load_barrier(uint32_t utype)
> +{
> +	if (utype == USE_MB)
> +		rte_mb();
> +	else if (utype == USE_SMP_MB)
> +		rte_smp_mb();
> +	else
> +		RTE_VERIFY(0);
> +}

It does not compile on ARM64.
I have sent a fix for ARM64 barrier macros:
	https://dpdk.org/patch/33762

  reply	other threads:[~2018-01-16  0:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 11:12 [dpdk-dev] [PATCH " Konstantin Ananyev
2017-12-01 11:12 ` [dpdk-dev] [PATCH 2/2] eal/x86: Use lock-prefixed instructions to reduce cost of rte_smp_mb() Konstantin Ananyev
2017-12-01 18:04   ` Stephen Hemminger
2017-12-01 23:08     ` Ananyev, Konstantin
2018-03-08 21:15       ` Stephen Hemminger
2017-12-11 17:11   ` Bruce Richardson
2017-12-11 17:30     ` Ananyev, Konstantin
2017-12-18 15:34   ` [dpdk-dev] [PATCH v2 0/2] eal/x86: Optimize rte_smp_mb() and create a new test case for it Konstantin Ananyev
2017-12-18 15:34   ` [dpdk-dev] [PATCH v2 1/2] test/test: introduce new test-case for rte_smp_mb() Konstantin Ananyev
2018-01-12 17:23     ` Thomas Monjalon
2018-01-12 17:58       ` Ananyev, Konstantin
2018-01-13 13:54     ` Wiles, Keith
2018-01-13 13:54     ` Wiles, Keith
2018-01-15 15:04     ` [dpdk-dev] [PATCH v3 0/2] eal/x86: Optimize rte_smp_mb() and create a new test case for it Konstantin Ananyev
2018-01-15 15:04     ` [dpdk-dev] [PATCH v3 1/2] test/test: introduce new test-case for rte_smp_mb() Konstantin Ananyev
2018-01-16  0:16       ` Thomas Monjalon [this message]
2018-01-15 15:04     ` [dpdk-dev] [PATCH v3 2/2] eal/x86: Use lock-prefixed instructions to reduce cost of rte_smp_mb() Konstantin Ananyev
2018-01-15 15:09       ` Konstantin Ananyev
     [not found]         ` <8b05f533-d146-7f97-48f4-82ddcfc3613b@redhat.com>
2018-01-16  1:54           ` [dpdk-dev] Fwd: " Michael S. Tsirkin
2018-01-29  9:29             ` Ananyev, Konstantin
2018-01-29 17:29               ` Michael S. Tsirkin
2018-01-29 15:47         ` [dpdk-dev] " Thomas Monjalon
2018-01-30 19:33           ` Stephen Hemminger
2017-12-18 15:34   ` [dpdk-dev] [PATCH v2 " Konstantin Ananyev
2017-12-18 15:46     ` Bruce Richardson
2017-12-11 17:08 ` [dpdk-dev] [PATCH 1/2] test/test: introduce new test-case for rte_smp_mb() 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=1920273.q5HlxWAJJN@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=konstantin.ananyev@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).