From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: olivier.matz@6wind.com, pbhagavatula@caviumnetworks.com
Cc: thomas@monjalon.net, dev@dpdk.org
Subject: [dpdk-dev] [PATCH 2/2] test: use the best mempool ops API to get mbuf pool
Date: Fri, 2 Feb 2018 01:17:07 +0530 [thread overview]
Message-ID: <1517514427-28843-2-git-send-email-hemant.agrawal@nxp.com> (raw)
In-Reply-To: <1517514427-28843-1-git-send-email-hemant.agrawal@nxp.com>
This patch replaces the uses of default mempool ops API
with newly supported best_mempool_ops API.
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
test/test/test_mempool.c | 3 ++-
test/test/test_mempool_perf.c | 5 +++--
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/test/test/test_mempool.c b/test/test/test_mempool.c
index f39df5a..63f921e 100644
--- a/test/test/test_mempool.c
+++ b/test/test/test_mempool.c
@@ -25,6 +25,7 @@
#include <rte_mempool.h>
#include <rte_spinlock.h>
#include <rte_malloc.h>
+#include <rte_mbuf_pool_ops.h>
#include "test.h"
@@ -485,7 +486,7 @@ test_mempool(void)
struct rte_mempool *mp_nocache = NULL;
struct rte_mempool *mp_stack = NULL;
struct rte_mempool *default_pool = NULL;
- const char *default_pool_ops = rte_eal_mbuf_default_mempool_ops();
+ const char *default_pool_ops = rte_mbuf_best_mempool_ops();
rte_atomic32_init(&synchro);
diff --git a/test/test/test_mempool_perf.c b/test/test/test_mempool_perf.c
index 70de0b3..dfeefab 100644
--- a/test/test/test_mempool_perf.c
+++ b/test/test/test_mempool_perf.c
@@ -25,7 +25,7 @@
#include <rte_mempool.h>
#include <rte_spinlock.h>
#include <rte_malloc.h>
-
+#include <rte_mbuf_pool_ops.h>
#include "test.h"
/*
@@ -308,7 +308,8 @@ test_mempool_perf(void)
if (mp_cache == NULL)
goto err;
- default_pool_ops = rte_eal_mbuf_default_mempool_ops();
+ default_pool_ops = rte_mbuf_best_mempool_ops();
+
/* Create a mempool based on Default handler */
default_pool = rte_mempool_create_empty("default_pool",
MEMPOOL_SIZE,
--
2.7.4
next prev parent reply other threads:[~2018-02-01 19:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 19:47 [dpdk-dev] [PATCH 1/2] Revert "eal: fix default mempool ops" Hemant Agrawal
2018-02-01 19:47 ` Hemant Agrawal [this message]
2018-02-01 19:56 ` Hemant Agrawal
2018-02-01 20:40 ` Pavan Nikhilesh
2018-02-02 5:43 ` Hemant Agrawal
2018-02-02 8:03 ` [dpdk-dev] [PATCH FIX-OPTION-2 1/2] eal: use named memzone to store user mempool ops name Hemant Agrawal
2018-02-02 8:03 ` [dpdk-dev] [PATCH FIX-OPTION-1] mbuf: fix the logic of user mempool ops API Hemant Agrawal
2018-02-02 13:40 ` Olivier Matz
2018-02-02 13:47 ` Hemant Agrawal
2018-02-06 0:05 ` Thomas Monjalon
[not found] ` <BY1PR0701MB1895B37B913A223180EED6D3EAFF0@BY1PR0701MB1895.namprd07.prod.outlook.com>
2018-02-04 6:34 ` [dpdk-dev] Fw: " santosh
2018-02-04 10:27 ` [dpdk-dev] " Hemant Agrawal
2018-02-02 8:03 ` [dpdk-dev] [PATCH FIX-OPTION-2 2/2] mbuf: fix user mempool ops get to use only named memzone Hemant Agrawal
2018-02-02 8:03 ` [dpdk-dev] [PATCH] doc: remove eal API for default mempool ops name Hemant Agrawal
2018-02-02 8:31 ` [dpdk-dev] [PATCH v2] " Hemant Agrawal
2018-02-02 14:01 ` Olivier Matz
2018-02-13 11:28 ` Ferruh Yigit
2018-02-14 14:58 ` Thomas Monjalon
2018-02-03 13:28 ` Jerin Jacob
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=1517514427-28843-2-git-send-email-hemant.agrawal@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=pbhagavatula@caviumnetworks.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).