From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: Juhamatti Kuusisaari <juhamatti.kuusisaari@coriant.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] lib: change rte_ring dequeue to guarantee ordering before tail update
Date: Fri, 15 Jul 2016 12:22:29 +0000 [thread overview]
Message-ID: <2601191342CEEE43887BDE71AB97725836B7E32F@irsmsx105.ger.corp.intel.com> (raw)
In-Reply-To: <20160715043951.32040-1-juhamatti.kuusisaari@coriant.com>
>
> Consumer queue dequeuing must be guaranteed to be done fully before the tail is updated. This is not guaranteed with a read barrier,
> changed to a write barrier just before tail update which in practice guarantees correct order of reads and writes.
>
> Signed-off-by: Juhamatti Kuusisaari <juhamatti.kuusisaari@coriant.com>
> ---
> lib/librte_ring/rte_ring.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/librte_ring/rte_ring.h b/lib/librte_ring/rte_ring.h index eb45e41..14920af 100644
> --- a/lib/librte_ring/rte_ring.h
> +++ b/lib/librte_ring/rte_ring.h
> @@ -748,7 +748,7 @@ __rte_ring_sc_do_dequeue(struct rte_ring *r, void **obj_table,
>
> /* copy in table */
> DEQUEUE_PTRS();
> - rte_smp_rmb();
> + rte_smp_wmb();
>
> __RING_STAT_ADD(r, deq_success, n);
> r->cons.tail = cons_next;
> --
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
> 2.9.0
>
next prev parent reply other threads:[~2016-07-15 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 4:39 Juhamatti Kuusisaari
2016-07-15 12:22 ` Ananyev, Konstantin [this message]
2016-07-21 21:26 ` Thomas Monjalon
2016-07-23 6:05 ` Jerin Jacob
2016-07-23 9:02 ` Thomas Monjalon
2016-07-23 9:36 ` Jerin Jacob
2016-07-23 10:14 ` Ananyev, Konstantin
2016-07-23 10:38 ` Jerin Jacob
2016-07-23 11:15 ` Ananyev, Konstantin
2016-07-23 11:49 ` Jerin Jacob
2016-07-23 12:32 ` Ananyev, Konstantin
2016-07-23 12:35 ` Jerin Jacob
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=2601191342CEEE43887BDE71AB97725836B7E32F@irsmsx105.ger.corp.intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=juhamatti.kuusisaari@coriant.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).