From: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>
To: jay.jayatheerthan@intel.com, jerinjacobk@gmail.com
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2] eventdev: fix event port setup in tx adapter
Date: Sat, 24 Jul 2021 08:54:13 -0500 [thread overview]
Message-ID: <20210724135413.912420-1-s.v.naga.harish.k@intel.com> (raw)
The event port config set by application in
rte_event_eth_tx_adapter_create API is modified in
default configuration callback function. This patch removes
this hardcode to use application provided event port
config value.
Fixes: ("eventdev: fix event port config override in tx adapter")
Signed-off-by: Naga Harish K, S V <s.v.naga.harish.k@intel.com>
---
lib/eventdev/rte_event_eth_tx_adapter.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/lib/eventdev/rte_event_eth_tx_adapter.c b/lib/eventdev/rte_event_eth_tx_adapter.c
index db260bfb68..18c0359db7 100644
--- a/lib/eventdev/rte_event_eth_tx_adapter.c
+++ b/lib/eventdev/rte_event_eth_tx_adapter.c
@@ -286,7 +286,6 @@ txa_service_conf_cb(uint8_t __rte_unused id, uint8_t dev_id,
return ret;
}
- pc->event_port_cfg = 0;
ret = rte_event_port_setup(dev_id, port_id, pc);
if (ret) {
RTE_EDEV_LOG_ERR("failed to setup event port %u\n",
--
2.25.1
next reply other threads:[~2021-07-24 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 13:54 Naga Harish K, S V [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-23 8:12 [dpdk-dev] [PATCH] eventdev: remove event port config override " Naga Harish K, S V
2021-07-24 14:10 ` [dpdk-dev] [PATCH v2] eventdev: fix event port setup " Naga Harish K, S V
2021-07-28 6:44 ` Jayatheerthan, Jay
2021-07-28 9:30 ` Jerin Jacob
2021-07-28 10:57 ` Jayatheerthan, Jay
2021-07-30 10:24 ` Jerin Jacob
2021-07-30 10:31 ` Thomas Monjalon
2021-07-30 10:36 ` Jerin Jacob
2021-07-30 10:59 ` 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=20210724135413.912420-1-s.v.naga.harish.k@intel.com \
--to=s.v.naga.harish.k@intel.com \
--cc=dev@dpdk.org \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinjacobk@gmail.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).