DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com,
	pablo.de.lara.guarch@intel.com, yipeng1.wang@intel.com,
	gavin.hu@arm.com, dharmik.thakkar@arm.com, nd@arm.com
Subject: Re: [dpdk-dev] [PATCH] doc/rel-notes: lock-free RW concurrency in hash
Date: Fri, 26 Oct 2018 12:55:39 +0200	[thread overview]
Message-ID: <1649799.5rOa2hZEDU@xps> (raw)
In-Reply-To: <1540356591-10745-1-git-send-email-honnappa.nagarahalli@arm.com>

24/10/2018 06:49, Honnappa Nagarahalli:
> Add lock-free reader/writer concurrency capability in rte_hash library
> to release notes.
> 
> Signed-off-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Reviewed-by: Gavin Hu <gavin.hu@arm.com>

Squashed in related patch

      reply	other threads:[~2018-10-26 10:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24  4:49 Honnappa Nagarahalli
2018-10-26 10:55 ` Thomas Monjalon [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=1649799.5rOa2hZEDU@xps \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=dharmik.thakkar@arm.com \
    --cc=gavin.hu@arm.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=nd@arm.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=yipeng1.wang@intel.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).