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: Thu, 31 May 2018 04:53:01 +0000 [thread overview]
Message-ID: <HE1PR0801MB1930F2C279038947D26DE1CD98630@HE1PR0801MB1930.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <86d0c839-8a45-9c6b-38e1-a196aafbd59f@intel.com>
No problem, it is still in programmer's guide :). I will rework the patch.
Thank you,
Honnappa
-----Original Message-----
From: Burakov, Anatoly <anatoly.burakov@intel.com>
Sent: Wednesday, May 30, 2018 2:48 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 5:36 PM, Honnappa Nagarahalli wrote:
> I do not see the documentation regarding this in programmer's guide.
Hi
Apologies, it's not in rte_ring section, it's in programmer's guide for EAL:
http://www.dpdk.org/doc/guides/prog_guide/env_abstraction_layer.html#known-issues
Perhaps this could be referenced in the rte_ring (or indeed copied/moved there)?
--
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.
next prev parent reply other threads:[~2018-05-31 4:53 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
2018-05-30 7:47 ` Burakov, Anatoly
2018-05-31 4:53 ` Honnappa Nagarahalli [this message]
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=HE1PR0801MB1930F2C279038947D26DE1CD98630@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).