From: Jerin Jacob <jerinjacobk@gmail.com>
To: Sunil Kumar Kori <skori@marvell.com>
Cc: "nipun.gupta@nxp.com" <nipun.gupta@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>,
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: Fri, 21 Jan 2022 17:28:59 +0530 [thread overview]
Message-ID: <CALBAE1N+FuOUrw1kn0-DE6oHA+gfjfZMNTcWiYk3keDaANhV0w@mail.gmail.com> (raw)
In-Reply-To: <CO6PR18MB3860F55B4FD88E3C715BEFC3B4589@CO6PR18MB3860.namprd18.prod.outlook.com>
On Tue, Jan 18, 2022 at 4:08 PM Sunil Kumar Kori <skori@marvell.com> wrote:
>
>
>
> 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
dequeuing
> >the API. This was not getting properly conigured in the application. This patch
configured
> >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>
> >---
>
> Acked-by: Sunil Kumar Kori <skori@mavell.com>
>
Fixed above typo
Applied to dpdk-next-net-eventdev/for-main. Thanks
prev parent reply other threads:[~2022-01-21 11:59 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 ` [EXT] " Sunil Kumar Kori
2022-01-21 11:58 ` Jerin Jacob [this message]
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=CALBAE1N+FuOUrw1kn0-DE6oHA+gfjfZMNTcWiYk3keDaANhV0w@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=nipun.gupta@nxp.com \
--cc=skori@marvell.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).