From: David Marchand <david.marchand@redhat.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 0/2] ring: empty optimization
Date: Wed, 1 Jul 2020 11:20:39 +0200 [thread overview]
Message-ID: <CAJFAV8zSjLtPSagKrrezC5nas898X9F7rRfi_f63nRMWnPTVQA@mail.gmail.com> (raw)
In-Reply-To: <20200519152725.63486-1-mb@smartsharesystems.com>
On Tue, May 19, 2020 at 5:27 PM Morten Brørup <mb@smartsharesystems.com> wrote:
>
> Testing if the ring is empty is as simple as comparing the producer and
> consumer pointers.
>
> Checkpatch complains about existing coding style violations, so the first
> part of the patch fixes those, and contains no functional changes.
>
> Morten Brørup (2):
> ring: coding style cleanup
> ring: empty optimization
>
> lib/librte_ring/rte_ring.c | 4 +--
> lib/librte_ring/rte_ring.h | 46 +++++++++++++++++----------------
> lib/librte_ring/rte_ring_elem.h | 10 +++----
> lib/librte_ring/rte_ring_hts.h | 8 +++---
> lib/librte_ring/rte_ring_rts.h | 8 +++---
> 5 files changed, 39 insertions(+), 37 deletions(-)
>
> --
> 2.17.1
>
Series applied, thanks.
--
David Marchand
prev parent reply other threads:[~2020-07-01 9:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 15:31 [dpdk-dev] [PATCH] ring: empty and count optimizations Morten Brørup
2020-05-13 15:35 ` Morten Brørup
2020-05-13 17:08 ` Morten Brørup
2020-05-14 12:23 ` Ananyev, Konstantin
2020-05-14 13:45 ` Morten Brørup
2020-05-14 16:46 ` Ananyev, Konstantin
2020-05-14 18:00 ` Morten Brørup
2020-05-19 15:27 ` [dpdk-dev] [PATCH 0/2] ring: empty optimization Morten Brørup
2020-05-19 15:27 ` [dpdk-dev] [PATCH 1/2] ring: coding style cleanup Morten Brørup
2020-05-22 12:34 ` Ananyev, Konstantin
2020-05-19 15:27 ` [dpdk-dev] [PATCH 2/2] ring: empty optimization Morten Brørup
2020-05-19 15:52 ` Stephen Hemminger
2020-05-19 16:02 ` Morten Brørup
2020-07-01 9:19 ` David Marchand
2020-05-22 12:32 ` Ananyev, Konstantin
2020-07-01 9:20 ` 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=CAJFAV8zSjLtPSagKrrezC5nas898X9F7rRfi_f63nRMWnPTVQA@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=mb@smartsharesystems.com \
--cc=nd@arm.com \
--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).