DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH] doc: add rcu defer queue API info
Date: Mon, 18 May 2020 17:53:48 +0200	[thread overview]
Message-ID: <CAJFAV8yL=XVxXNvJb=9Ku9sJ2319DX7QpumLYPoO+TR9mGq=6g@mail.gmail.com> (raw)
In-Reply-To: <20200506035415.29095-1-honnappa.nagarahalli@arm.com>

On Wed, May 6, 2020 at 5:54 AM Honnappa Nagarahalli
<honnappa.nagarahalli@arm.com> wrote:
>
> Added notes about RCU defer queue APIs.
>
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> ---
>  doc/guides/rel_notes/release_20_05.rst | 7 +++++++
>  1 file changed, 7 insertions(+)
>
> diff --git a/doc/guides/rel_notes/release_20_05.rst b/doc/guides/rel_notes/release_20_05.rst
> index c287cb48a..0d505d7f1 100644
> --- a/doc/guides/rel_notes/release_20_05.rst
> +++ b/doc/guides/rel_notes/release_20_05.rst
> @@ -66,6 +66,13 @@ New Features
>    Added tracepoints in ``EAL``, ``ethdev``, ``cryptodev``, ``eventdev`` and
>    ``mempool`` libraries for important functions.
>
> +* **Added APIs for RCU defer queue**
> +
> +  Added APIs to create and delete defer queue. Additional APIs are provided
> +  to enqueue a deleted resource and reclaim the resource in the future.
> +  These APIs help the application use lock-free data structures with
> +  less effort.
> +
>  * **Added new API for rte_ring.**
>
>    * New synchronization modes for rte_ring.
> --
> 2.17.1
>

Applied, thanks.


-- 
David Marchand


      reply	other threads:[~2020-05-18 15:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06  3:54 Honnappa Nagarahalli
2020-05-18 15:53 ` David Marchand [this message]

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='CAJFAV8yL=XVxXNvJb=9Ku9sJ2319DX7QpumLYPoO+TR9mGq=6g@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=thomas@monjalon.net \
    /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).