From: Thomas Monjalon <thomas@monjalon.net>
To: Gavin Hu <gavin.hu@arm.com>
Cc: dev@dpdk.org, nd@arm.com, jerin.jacob@caviumnetworks.com,
hemant.agrawal@nxp.com, Honnappa.Nagarahalli@arm.com,
bruce.richardson@intel.com, Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/2] add rte ring reset api and use it to flush a ring by hash
Date: Wed, 19 Dec 2018 22:59:04 +0100 [thread overview]
Message-ID: <3213509.eEyrQtEzxV@xps> (raw)
In-Reply-To: <20181212111525.22996-1-gavin.hu@arm.com>
+Cc Olivier, maintainer of the ring library.
12/12/2018 12:15, Gavin Hu:
> V3: Allow experimental API for meson build
>
> V2: Fix the coding style issue(commit message line too long)
>
> V1: To flush a ring not in use, dequeue one by one is wasting cpu cycles.
> The patch is to just resetting the head and tail indices to save cpu
> cycle.
>
> Gavin Hu (2):
> ring: add reset api to flush the ring when not in use
> hash: flush the rings instead of dequeuing one by one
>
> lib/librte_hash/Makefile | 2 +-
> lib/librte_hash/meson.build | 3 +++
> lib/librte_hash/rte_cuckoo_hash.c | 11 ++++-------
> lib/librte_ring/rte_ring.h | 20 ++++++++++++++++++++
> lib/librte_ring/rte_ring_version.map | 7 +++++++
> 5 files changed, 35 insertions(+), 8 deletions(-)
prev parent reply other threads:[~2018-12-19 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 11:15 Gavin Hu
2018-12-12 11:15 ` [dpdk-dev] [PATCH v3 1/2] ring: add reset api to flush the ring when not in use Gavin Hu
2018-12-12 11:15 ` [dpdk-dev] [PATCH v3 2/2] hash: flush the rings instead of dequeuing one by one Gavin Hu
2018-12-19 21:59 ` 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=3213509.eEyrQtEzxV@xps \
--to=thomas@monjalon.net \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=gavin.hu@arm.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.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).