DPDK patches and discussions
 help / color / mirror / Atom feed
From: gavin hu <gavin.hu@arm.com>
To: dev@dpdk.org
Cc: nd@arm.com, thomas@monjalon.net, jerinj@marvell.com,
	hemant.agrawal@nxp.com, Honnappa.Nagarahalli@arm.com,
	gavin.hu@arm.com, olivier.matz@6wind.com,
	bruce.richardson@intel.com
Subject: [dpdk-dev] [PATCH v6 0/3] ring test enhancement and new ring reset api and use it by hash
Date: Wed,  9 Jan 2019 19:31:39 +0800	[thread overview]
Message-ID: <1547033502-3167-1-git-send-email-gavin.hu@arm.com> (raw)
In-Reply-To: <1546483094-29712-2-git-send-email-gavin.hu@arm.com>

V6: Made upper case for the user name to comply with the convention.

V5:
1. Commit message tweaking for ring test case enhancement patch
2. Upper to lower for mails to make match/grep more easily

V4: 
1. Include the ring perf test case enhancement patch in the series.
2. Replace ARRAY_SIZE with RTE_DIM.
3. Call memset to avoid clang compling complains.

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

Joyce Kong (1):
  test/ring: ring perf test case enhancement

 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 +++
 test/test/test_ring_perf.c           | 82 ++++++++++++++++++++++++++++++++++--
 6 files changed, 114 insertions(+), 11 deletions(-)

-- 
2.7.4

  parent reply	other threads:[~2019-01-09 11:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-02  0:55 [dpdk-dev] [PATCH v4 0/3] add rte ring reset api and use it to flush a ring " Gavin Hu
2019-01-02  0:55 ` [dpdk-dev] [PATCH v4 1/3] test/ring: ring perf test case enhancement Gavin Hu
2019-01-02 12:49   ` Thomas Monjalon
2019-01-03  2:40     ` Gavin Hu (Arm Technology China)
2019-01-02  0:55 ` [dpdk-dev] [PATCH v4 2/3] ring: add reset api to flush the ring when not in use Gavin Hu
2019-01-02  0:55 ` [dpdk-dev] [PATCH v4 3/3] hash: flush the rings instead of dequeuing one by one Gavin Hu
2019-01-02 12:50 ` [dpdk-dev] [PATCH v4 0/3] add rte ring reset api and use it to flush a ring by hash Thomas Monjalon
2019-01-02 18:40   ` Honnappa Nagarahalli
2019-01-03  2:43     ` Gavin Hu (Arm Technology China)
2019-01-03  2:38 ` [dpdk-dev] [PATCH v5 0/3] ring test enhancement and new ring reset api and use it " gavin hu
2019-01-03  2:38   ` [dpdk-dev] [PATCH v5 1/3] test/ring: ring perf test case enhancement gavin hu
2019-01-03  7:39     ` Thomas Monjalon
2019-01-03  8:22       ` Gavin Hu (Arm Technology China)
2019-01-09 11:31     ` gavin hu [this message]
2019-01-09 11:31     ` [dpdk-dev] [PATCH v6 " gavin hu
2019-09-09  5:19       ` [dpdk-dev] [PATCH v7] " Joyce Kong
2019-10-08  8:07         ` Olivier Matz
2019-10-24  7:56           ` David Marchand
2019-01-09 11:31     ` [dpdk-dev] [PATCH v6 2/3] ring: add reset API to flush the ring when not in use gavin hu
2019-01-09 11:31     ` [dpdk-dev] [PATCH v6 3/3] hash: flush the rings instead of dequeuing one by one gavin hu
2019-01-09 18:53       ` Wang, Yipeng1
2019-01-03  2:38   ` [dpdk-dev] [PATCH v5 2/3] ring: add reset API to flush the ring when not in use gavin hu
2019-01-03  2:38   ` [dpdk-dev] [PATCH v5 3/3] hash: flush the rings instead of dequeuing one by one gavin hu

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=1547033502-3167-1-git-send-email-gavin.hu@arm.com \
    --to=gavin.hu@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=nd@arm.com \
    --cc=olivier.matz@6wind.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).