DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
	"olivier.matz@6wind.com" <olivier.matz@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] rte_ring: clarify preemptible nature of ring algorithm
Date: Tue, 29 May 2018 16:36:23 +0000	[thread overview]
Message-ID: <HE1PR0801MB1930B3E1741C797BEF941D82986D0@HE1PR0801MB1930.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <3b43c395-2ebd-228a-23be-cbe149e4c812@intel.com>

I do not see the documentation regarding this in programmer's guide.

-----Original Message-----
From: Burakov, Anatoly <anatoly.burakov@intel.com>
Sent: Tuesday, May 29, 2018 4:10 AM
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>; olivier.matz@6wind.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] rte_ring: clarify preemptible nature of ring algorithm

On 29-May-18 6:28 AM, Honnappa Nagarahalli wrote:
> rte_ring implementation is not preemptible only under certain
> circumstances. This clarification is helpful for data plane and
> control plane communication using rte_ring.
>
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
> Reviewed-by: Ola Liljedahl <ola.liljedahl@arm.com>
> ---
> v2:
> * Fixed checkpatch warnings
>
>   lib/librte_ring/rte_ring.h | 9 +++++++--
>   1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/lib/librte_ring/rte_ring.h b/lib/librte_ring/rte_ring.h
> index d3d3f7f..2f9c945 100644
> --- a/lib/librte_ring/rte_ring.h
> +++ b/lib/librte_ring/rte_ring.h
> @@ -26,8 +26,13 @@
>    * - Bulk dequeue.
>    * - Bulk enqueue.
>    *
> - * Note: the ring implementation is not preemptable. A lcore must not
> - * be interrupted by another task that uses the same ring.
> + * Note: the ring implementation can block threads from completing
> + their
> + * operation under the following circumstances.
> + * A preempted thread can block other threads (operating on the same
> + ring)
> + * from completing their operations, only if those threads are
> + performing
> + * the same ring operation (enqueue/dequeue) as the preempted thread.
> + * In other words, a preempted consumer thread will not block any
> + producer
> + * threads and vice versa.
>    *
>    */
>
>

Similar clarification is already present in Programmer's Guide for rte_ring section. Perhaps it would be good to reference it here?

--
Thanks,
Anatoly
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  reply	other threads:[~2018-05-29 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-29  5:28 Honnappa Nagarahalli
2018-05-29  9:09 ` Burakov, Anatoly
2018-05-29 16:36   ` Honnappa Nagarahalli [this message]
2018-05-30  7:47     ` Burakov, Anatoly
2018-05-31  4:53       ` Honnappa Nagarahalli
2018-06-25 15:37         ` Olivier Matz
2018-07-10  0:16           ` Honnappa Nagarahalli

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=HE1PR0801MB1930B3E1741C797BEF941D82986D0@HE1PR0801MB1930.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=olivier.matz@6wind.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).