From: <pbhagavatula@marvell.com>
To: <jerinj@marvell.com>, Sunil Kumar Kori <skori@marvell.com>,
"Pavan Nikhilesh" <pbhagavatula@marvell.com>
Cc: <dev@dpdk.org>, <jay.jayatheerthan@intel.com>,
<erik.g.carrillo@intel.com>, <abhinandan.gujjar@intel.com>,
<timothy.mcdaniel@intel.com>, <sthotton@marvell.com>,
<hemant.agrawal@nxp.com>, <nipun.gupta@nxp.com>,
<harry.van.haaren@intel.com>, <mattias.ronnblom@ericsson.com>,
<liangma@liangbit.com>, <peter.mccarthy@intel.com>
Subject: [PATCH 2/3] examples: update event vector free routine
Date: Tue, 16 Aug 2022 21:19:31 +0530 [thread overview]
Message-ID: <20220816154932.10168-2-pbhagavatula@marvell.com> (raw)
In-Reply-To: <20220816154932.10168-1-pbhagavatula@marvell.com>
From: Pavan Nikhilesh <pbhagavatula@marvell.com>
Update event vector free routine to account for element
offset while freeing elements.
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
app/test-eventdev/test_pipeline_common.c | 5 +++--
examples/l2fwd-event/l2fwd_common.c | 5 +++--
examples/l3fwd/l3fwd_event.c | 5 +++--
3 files changed, 9 insertions(+), 6 deletions(-)
diff --git a/app/test-eventdev/test_pipeline_common.c b/app/test-eventdev/test_pipeline_common.c
index 4f40d37659..4404c665f5 100644
--- a/app/test-eventdev/test_pipeline_common.c
+++ b/app/test-eventdev/test_pipeline_common.c
@@ -673,8 +673,9 @@ pipeline_vector_array_free(struct rte_event events[], uint16_t num)
uint16_t i;
for (i = 0; i < num; i++) {
- rte_pktmbuf_free_bulk(events[i].vec->mbufs,
- events[i].vec->nb_elem);
+ rte_pktmbuf_free_bulk(
+ &events[i].vec->mbufs[events[i].vec->elem_offset],
+ events[i].vec->nb_elem - events[i].vec->elem_offset);
rte_mempool_put(rte_mempool_from_obj(events[i].vec),
events[i].vec);
}
diff --git a/examples/l2fwd-event/l2fwd_common.c b/examples/l2fwd-event/l2fwd_common.c
index 41a0d3f22f..5af7fa6127 100644
--- a/examples/l2fwd-event/l2fwd_common.c
+++ b/examples/l2fwd-event/l2fwd_common.c
@@ -121,8 +121,9 @@ l2fwd_event_vector_array_free(struct rte_event events[], uint16_t num)
uint16_t i;
for (i = 0; i < num; i++) {
- rte_pktmbuf_free_bulk(events[i].vec->mbufs,
- events[i].vec->nb_elem);
+ rte_pktmbuf_free_bulk(
+ &events[i].vec->mbufs[events[i].vec->elem_offset],
+ events[i].vec->nb_elem - events[i].vec->elem_offset);
rte_mempool_put(rte_mempool_from_obj(events[i].vec),
events[i].vec);
}
diff --git a/examples/l3fwd/l3fwd_event.c b/examples/l3fwd/l3fwd_event.c
index 0b58475c85..984dad1ece 100644
--- a/examples/l3fwd/l3fwd_event.c
+++ b/examples/l3fwd/l3fwd_event.c
@@ -294,8 +294,9 @@ l3fwd_event_vector_array_free(struct rte_event events[], uint16_t num)
uint16_t i;
for (i = 0; i < num; i++) {
- rte_pktmbuf_free_bulk(events[i].vec->mbufs,
- events[i].vec->nb_elem);
+ rte_pktmbuf_free_bulk(
+ &events[i].vec->mbufs[events[i].vec->elem_offset],
+ events[i].vec->nb_elem - events[i].vec->elem_offset);
rte_mempool_put(rte_mempool_from_obj(events[i].vec),
events[i].vec);
}
--
2.25.1
next prev parent reply other threads:[~2022-08-16 15:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 15:49 [PATCH 1/3] eventdev: add element offset to event vector pbhagavatula
2022-08-16 15:49 ` pbhagavatula [this message]
2022-08-16 15:49 ` [PATCH 3/3] event/cnxk: update event vector Tx routine pbhagavatula
2022-08-18 16:28 ` [PATCH 1/3] eventdev: add element offset to event vector Mattias Rönnblom
2022-08-23 20:39 ` [EXT] " Pavan Nikhilesh Bhagavatula
2022-08-24 8:41 ` Mattias Rönnblom
2022-08-29 8:47 ` Pavan Nikhilesh Bhagavatula
2022-09-14 13:02 ` Jerin Jacob
2022-09-14 14:55 ` Mattias Rönnblom
2022-09-21 16:43 ` [PATCH v2 " pbhagavatula
2022-09-21 16:43 ` [PATCH v2 2/3] examples: update event vector free routine pbhagavatula
2022-09-21 16:43 ` [PATCH v2 3/3] event/cnxk: update event vector Tx routine pbhagavatula
2022-09-22 5:40 ` [PATCH v2 1/3] eventdev: add element offset to event vector Mattias Rönnblom
2022-09-27 13:42 ` 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=20220816154932.10168-2-pbhagavatula@marvell.com \
--to=pbhagavatula@marvell.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinj@marvell.com \
--cc=liangma@liangbit.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=nipun.gupta@nxp.com \
--cc=peter.mccarthy@intel.com \
--cc=skori@marvell.com \
--cc=sthotton@marvell.com \
--cc=timothy.mcdaniel@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).