From: Harman Kalra <hkalra@marvell.com>
To: "reshma.pattan@intel.com" <reshma.pattan@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Harman Kalra <hkalra@marvell.com>
Subject: [dpdk-dev] [PATCH] app/pdump: enforcing pdump to use sw mempool
Date: Fri, 15 Mar 2019 15:27:41 +0000 [thread overview]
Message-ID: <1552663632-18742-1-git-send-email-hkalra@marvell.com> (raw)
Message-ID: <20190315152741.FuFO2-6VsAHSisRD3zNa3_o4MDDZD0qmzcXkHRDr4II@z> (raw)
Since pdump uses SW rings to manage packets hence
pdump should use SW ring mempool for managing its
own copy of packets.
Signed-off-by: Harman Kalra <hkalra@marvell.com>
---
app/pdump/main.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/app/pdump/main.c b/app/pdump/main.c
index ccf2a1d2f..d0e342645 100644
--- a/app/pdump/main.c
+++ b/app/pdump/main.c
@@ -598,11 +598,12 @@ create_mp_ring_vdev(void)
mbuf_pool = rte_mempool_lookup(mempool_name);
if (mbuf_pool == NULL) {
/* create mempool */
- mbuf_pool = rte_pktmbuf_pool_create(mempool_name,
+ mbuf_pool = rte_pktmbuf_pool_create_by_ops(mempool_name,
pt->total_num_mbufs,
MBUF_POOL_CACHE_SIZE, 0,
pt->mbuf_data_size,
- rte_socket_id());
+ rte_socket_id(),
+ RTE_MBUF_DEFAULT_MEMPOOL_OPS);
if (mbuf_pool == NULL) {
cleanup_rings();
rte_exit(EXIT_FAILURE,
--
2.18.0
next reply other threads:[~2019-03-15 15:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 15:27 Harman Kalra [this message]
2019-03-15 15:27 ` Harman Kalra
2019-07-04 16:29 ` Thomas Monjalon
2019-07-05 13:48 ` Olivier Matz
2019-07-05 14:39 ` [dpdk-dev] [EXT] " Harman Kalra
2019-07-05 15:09 ` Thomas Monjalon
2019-07-05 15:40 ` [dpdk-dev] [PATCH v2] " Harman Kalra
2019-07-05 15:50 ` Olivier Matz
2019-07-09 8:44 ` [dpdk-dev] [PATCH v3] " Harman Kalra
2019-07-10 9:22 ` [dpdk-dev] [PATCH v4] app/pdump: enforcing pdump to use SW mempool Harman Kalra
2019-07-10 22:21 ` Thomas Monjalon
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=1552663632-18742-1-git-send-email-hkalra@marvell.com \
--to=hkalra@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=reshma.pattan@intel.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).