DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
	dev <dev@dpdk.org>,
	 "Ruifeng Wang (Arm Technology China)" <ruifeng.wang@arm.com>,
	dpdk stable <stable@dpdk.org>, nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH 0/7] typo, doc, simple fixes and some optimizations
Date: Mon, 21 Oct 2019 21:19:55 +0200	[thread overview]
Message-ID: <CAJFAV8wnrWnjgT3ZEf9LrQPxL5iY1YBEV=YuA0TMv3ZFf3XQ7Q@mail.gmail.com> (raw)
In-Reply-To: <20191008211220.31586-1-honnappa.nagarahalli@arm.com>

On Tue, Oct 8, 2019 at 11:12 PM Honnappa Nagarahalli
<honnappa.nagarahalli@arm.com> wrote:
>
> Few typo fixes, some corrections to the documentation and simple fixes to
> the test cases.
>
> The last 2 commits contain simple optimizations with good amount of
> performance improvements.

Do you have numbers to illustrate?

>
> v2:
>   All instances of size_t fixed (Ruifeng)
>
> Honnappa Nagarahalli (7):
>   doc/rcu: fix typos
>   doc/rcu: correct the limitation on number of threads
>   doc/rcu: add information about storing token and resource
>   test/rcu: use size_t instead of int
>   test/rcu: use correct nomenclature while printing results
>   lib/rcu: add least acknowledged token optimization
>   lib/rcu: update QS only when there are updates from writer

Series applied, thanks.


--
David Marchand


  parent reply	other threads:[~2019-10-21 19:20 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08 21:12 Honnappa Nagarahalli
2019-10-08 21:12 ` [dpdk-dev] [PATCH v2 1/7] doc/rcu: fix typos Honnappa Nagarahalli
2019-10-08 21:12 ` [dpdk-dev] [PATCH v2 2/7] doc/rcu: correct the limitation on number of threads Honnappa Nagarahalli
2019-10-08 21:12 ` [dpdk-dev] [PATCH v2 3/7] doc/rcu: add information about storing token and resource Honnappa Nagarahalli
2019-10-08 21:12 ` [dpdk-dev] [PATCH v2 4/7] test/rcu: use size_t instead of int Honnappa Nagarahalli
2019-10-21 19:19   ` David Marchand
2019-10-08 21:12 ` [dpdk-dev] [PATCH v2 5/7] test/rcu: use correct nomenclature while printing results Honnappa Nagarahalli
2019-10-08 21:12 ` [dpdk-dev] [PATCH v2 6/7] lib/rcu: add least acknowledged token optimization Honnappa Nagarahalli
2019-10-08 21:12 ` [dpdk-dev] [PATCH v2 7/7] lib/rcu: update QS only when there are updates from writer Honnappa Nagarahalli
2019-10-18  9:57 ` [dpdk-dev] [PATCH] rcu: fix reference to offline function David Marchand
2019-10-18 13:58   ` Honnappa Nagarahalli
2019-10-21 19:25     ` David Marchand
2019-10-21 19:19 ` David Marchand [this message]
2019-10-21 19:39   ` [dpdk-dev] [PATCH 0/7] typo, doc, simple fixes and some optimizations Honnappa Nagarahalli
  -- strict thread matches above, loose matches on Subject: below --
2019-09-08 22:49 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='CAJFAV8wnrWnjgT3ZEf9LrQPxL5iY1YBEV=YuA0TMv3ZFf3XQ7Q@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=nd@arm.com \
    --cc=ruifeng.wang@arm.com \
    --cc=stable@dpdk.org \
    /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).