From: "Mauricio Vásquez" <mauricio.vasquezbernal@studenti.polito.it>
To: Lazaros Koromilas <l@nofutznetworks.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] ring: check for zero objects mc dequeue / mp enqueue
Date: Thu, 17 Mar 2016 17:09:08 +0100 [thread overview]
Message-ID: <CAPwdgqj8TRTAa8wRqmKZ3PT-2K6nbS8AAYfOrk=mcO_isU_W7g@mail.gmail.com> (raw)
In-Reply-To: <1458229783-15547-1-git-send-email-l@nofutznetworks.com>
Hi Lazaros,
On Thu, Mar 17, 2016 at 4:49 PM, Lazaros Koromilas <l@nofutznetworks.com>
wrote:
> Issuing a zero objects dequeue with a single consumer has no effect.
> Doing so with multiple consumers, can get more than one thread to succeed
> the compare-and-set operation and observe starvation or even deadlock in
> the while loop that checks for preceding dequeues. The problematic piece
> of code when n = 0:
>
> cons_next = cons_head + n;
> success = rte_atomic32_cmpset(&r->cons.head, cons_head, cons_next);
>
> The same is possible on the enqueue path.
>
> Signed-off-by: Lazaros Koromilas <l@nofutznetworks.com>
> ---
> lib/librte_ring/rte_ring.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/lib/librte_ring/rte_ring.h b/lib/librte_ring/rte_ring.h
> index 943c97c..eb45e41 100644
> --- a/lib/librte_ring/rte_ring.h
> +++ b/lib/librte_ring/rte_ring.h
> @@ -431,6 +431,11 @@ __rte_ring_mp_do_enqueue(struct rte_ring *r, void *
> const *obj_table,
> uint32_t mask = r->prod.mask;
> int ret;
>
> + /* Avoid the unnecessary cmpset operation below, which is also
> + * potentially harmful when n equals 0. */
> + if (n == 0)
>
What about using unlikely here?
> + return 0;
> +
> /* move prod.head atomically */
> do {
> /* Reset n to the initial burst count */
> @@ -618,6 +623,11 @@ __rte_ring_mc_do_dequeue(struct rte_ring *r, void
> **obj_table,
> unsigned i, rep = 0;
> uint32_t mask = r->prod.mask;
>
> + /* Avoid the unnecessary cmpset operation below, which is also
> + * potentially harmful when n equals 0. */
> + if (n == 0)
>
Also here.
> + return 0;
> +
> /* move cons.head atomically */
> do {
> /* Restore n as it may change every loop */
> --
> 1.9.1
>
>
next prev parent reply other threads:[~2016-03-17 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 15:49 Lazaros Koromilas
2016-03-17 16:09 ` Mauricio Vásquez [this message]
2016-03-18 10:18 ` Bruce Richardson
2016-03-18 10:27 ` Olivier Matz
2016-03-18 10:35 ` Bruce Richardson
2016-03-18 10:35 ` Thomas Monjalon
2016-03-18 12:47 ` Mauricio Vásquez
2016-03-18 14:16 ` Bruce Richardson
2016-03-21 17:47 ` Xie, Huawei
2016-03-22 10:13 ` Bruce Richardson
2016-03-22 14:38 ` Xie, Huawei
2016-03-21 12:23 ` Olivier Matz
2016-03-22 16:49 ` Thomas Monjalon
2016-03-25 11:15 ` Olivier Matz
2016-03-28 15:48 ` Lazaros Koromilas
2016-03-29 8:54 ` Bruce Richardson
2016-03-29 15:29 ` Olivier MATZ
2016-03-29 16:04 ` Bruce Richardson
2016-03-29 17:35 ` Lazaros Koromilas
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='CAPwdgqj8TRTAa8wRqmKZ3PT-2K6nbS8AAYfOrk=mcO_isU_W7g@mail.gmail.com' \
--to=mauricio.vasquezbernal@studenti.polito.it \
--cc=dev@dpdk.org \
--cc=l@nofutznetworks.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).