From: Jerin Jacob <jerinjacobk@gmail.com>
To: Rahul Bhansali <rbhansali@marvell.com>
Cc: dev@dpdk.org, Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Harman Kalra <hkalra@marvell.com>,
jerinj@marvell.com
Subject: Re: [PATCH] common/cnxk: fix loopback port dataflow issue
Date: Mon, 4 Mar 2024 22:05:10 +0530 [thread overview]
Message-ID: <CALBAE1OPyVLTXG7h6rh2c-NWjebX8RWB3kmnGKiY+H8rXf1yTg@mail.gmail.com> (raw)
In-Reply-To: <20240304123335.1769854-1-rbhansali@marvell.com>
On Mon, Mar 4, 2024 at 6:10 PM Rahul Bhansali <rbhansali@marvell.com> wrote:
>
> With loopback interface and IPsec Inbound traffic, getting
> NIX_CQERRINT_CPT_DROP interrupt and dataflow is stopped.
> This is due to flow control configuration is skipped as
> roc_nix_is_esw() returns true for loopback device also.
>
> Fixes: 978dc3a13f7b ("common/cnxk: base support for eswitch VF")
> Fixes: f812768a9e66 ("net/cnxk: support eswitch VF as ethernet device")
>
> Signed-off-by: Rahul Bhansali <rbhansali@marvell.com>
Applied to dpdk-next-net-mrvl/for-main. Thanks
> ---
> drivers/common/cnxk/roc_nix.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/common/cnxk/roc_nix.c b/drivers/common/cnxk/roc_nix.c
> index 20202788b5..041621dfaa 100644
> --- a/drivers/common/cnxk/roc_nix.c
> +++ b/drivers/common/cnxk/roc_nix.c
> @@ -385,8 +385,9 @@ sdp_lbk_id_update(struct plt_pci_device *pci_dev, struct nix *nix)
> nix->sdp_link = true;
> break;
> case PCI_DEVID_CNXK_RVU_AF_VF:
> - case PCI_DEVID_CNXK_RVU_ESWITCH_VF:
> nix->lbk_link = true;
> + break;
> + case PCI_DEVID_CNXK_RVU_ESWITCH_VF:
> nix->esw_link = true;
> break;
> default:
> --
> 2.25.1
>
prev parent reply other threads:[~2024-03-04 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 12:33 Rahul Bhansali
2024-03-04 16:35 ` 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=CALBAE1OPyVLTXG7h6rh2c-NWjebX8RWB3kmnGKiY+H8rXf1yTg@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=rbhansali@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).