From: Sunil Kumar Kori <skori@marvell.com>
To: "nipun.gupta@nxp.com" <nipun.gupta@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [EXT] [PATCH] examples/l3fwd: fix Rx burst size for event mode
Date: Tue, 18 Jan 2022 10:38:38 +0000 [thread overview]
Message-ID: <CO6PR18MB3860F55B4FD88E3C715BEFC3B4589@CO6PR18MB3860.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20220111050546.13003-1-nipun.gupta@nxp.com>
Regards
Sunil Kumar Kori
>-----Original Message-----
>From: nipun.gupta@nxp.com <nipun.gupta@nxp.com>
>Sent: Tuesday, January 11, 2022 10:36 AM
>To: dev@dpdk.org
>Cc: Jerin Jacob Kollanukkaran <jerinj@marvell.com>; Sunil Kumar Kori
><skori@marvell.com>; thomas@monjalon.net; hemant.agrawal@nxp.com;
>stable@dpdk.org; Nipun Gupta <nipun.gupta@nxp.com>
>Subject: [EXT] [PATCH] examples/l3fwd: fix Rx burst size for event mode
>
>External Email
>
>----------------------------------------------------------------------
>From: Nipun Gupta <nipun.gupta@nxp.com>
>
>While dequeing the packets from the event device, burst size is provided in
>the API. This was not getting properly conigured in the application. This patch
>correctly configures the burst size.
>
>Fixes: aaf58cb85b62 ("examples/l3fwd: add event port and queue setup")
>Cc: stable@dpdk.org
>
>Signed-off-by: Nipun Gupta <nipun.gupta@nxp.com>
>---
> examples/l3fwd/l3fwd_event_internal_port.c | 2 ++
> 1 file changed, 2 insertions(+)
>
>diff --git a/examples/l3fwd/l3fwd_event_internal_port.c
>b/examples/l3fwd/l3fwd_event_internal_port.c
>index 1e8f46bc11..32cf657148 100644
>--- a/examples/l3fwd/l3fwd_event_internal_port.c
>+++ b/examples/l3fwd/l3fwd_event_internal_port.c
>@@ -118,6 +118,8 @@ l3fwd_event_port_setup_internal_port(void)
> event_p_conf.event_port_cfg |=
> RTE_EVENT_PORT_CFG_DISABLE_IMPL_REL;
>
>+ evt_rsrc->deq_depth = def_p_conf.dequeue_depth;
>+
> for (event_p_id = 0; event_p_id < evt_rsrc->evp.nb_ports;
> event_p_id++)
>{
> ret = rte_event_port_setup(event_d_id, event_p_id,
>--
>2.17.1
Acked-by: Sunil Kumar Kori <skori@mavell.com>
next prev parent reply other threads:[~2022-01-18 10:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 5:05 nipun.gupta
2022-01-18 10:38 ` Sunil Kumar Kori [this message]
2022-01-21 11:58 ` [EXT] " 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=CO6PR18MB3860F55B4FD88E3C715BEFC3B4589@CO6PR18MB3860.namprd18.prod.outlook.com \
--to=skori@marvell.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=nipun.gupta@nxp.com \
--cc=stable@dpdk.org \
--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).