From: Nipun Gupta <nipun.gupta@nxp.com>
To: dev@dpdk.org
Cc: pbhagavatula@marvell.com, jerinj@marvell.com,
hemant.agrawal@nxp.com, akhil.goyal@nxp.com,
marko.kovacevic@intel.com, orika@mellanox.com,
bruce.richardson@intel.com, radu.nicolau@intel.com,
tomasz.kantecki@intel.com, skori@marvell.com,
Nipun Gupta <nipun.gupta@nxp.com>
Subject: [dpdk-dev] [PATCH 1/2] examples/l3fwd: set default schedule type as atomic
Date: Mon, 6 Jan 2020 10:04:44 +0530 [thread overview]
Message-ID: <20200106043445.14334-1-nipun.gupta@nxp.com> (raw)
Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
---
These patches are based over https://patchwork.dpdk.org/patch/63553/.
Feel free to merge into the series.
examples/l3fwd/l3fwd_event.h | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/examples/l3fwd/l3fwd_event.h b/examples/l3fwd/l3fwd_event.h
index fcc0ce51a..470aedc61 100644
--- a/examples/l3fwd/l3fwd_event.h
+++ b/examples/l3fwd/l3fwd_event.h
@@ -100,7 +100,11 @@ l3fwd_get_eventdev_rsrc(void)
mz = rte_memzone_reserve(name, sizeof(struct l3fwd_event_resources),
0, 0);
if (mz != NULL) {
+ struct l3fwd_event_resources *rsrc = mz->addr;
+
memset(mz->addr, 0, sizeof(struct l3fwd_event_resources));
+ rsrc->sched_type = RTE_SCHED_TYPE_ATOMIC;
+
return mz->addr;
}
--
2.17.1
next reply other threads:[~2020-01-06 4:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 4:34 Nipun Gupta [this message]
2020-01-06 4:34 ` [dpdk-dev] [PATCH 2/2] examples/l3fwd: support multiple queues in event mode Nipun Gupta
2020-01-06 6:09 ` [dpdk-dev] [EXT] " Sunil Kumar Kori
2020-01-06 17:47 ` Nipun Gupta
2020-01-07 12:22 ` [dpdk-dev] [PATCH 1/2 v2] examples/l3fwd: set default schedule type as atomic Nipun Gupta
2020-01-07 12:22 ` [dpdk-dev] [PATCH 2/2 v2] examples/l3fwd: support multiple eth Rx queues in event mode Nipun Gupta
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=20200106043445.14334-1-nipun.gupta@nxp.com \
--to=nipun.gupta@nxp.com \
--cc=akhil.goyal@nxp.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=marko.kovacevic@intel.com \
--cc=orika@mellanox.com \
--cc=pbhagavatula@marvell.com \
--cc=radu.nicolau@intel.com \
--cc=skori@marvell.com \
--cc=tomasz.kantecki@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).