From: Amiya Ranjan Mohakud <amiyaranjan.mohakud@gmail.com>
To: "Loftus, Ciara" <ciara.loftus@intel.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH v3] net/iavf: fix VLAN offload strip flag
Date: Thu, 3 Jul 2025 13:55:19 +0530 [thread overview]
Message-ID: <CAL+mCpPA5c6yVg4OhSFH2a5ymp11b7go+SnqP-rgh4gYBCK2uw@mail.gmail.com> (raw)
In-Reply-To: <DM3PPF7D18F34A1E4C9969B1703BF0F09B18E43A@DM3PPF7D18F34A1.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 3016 bytes --]
Sure Ciara. Thanks.
I will raise a fresh new patch for bug Id: 1735. That would be better.
Thanks
Amiya
On Thu, 3 Jul 2025 at 13:48, Loftus, Ciara <ciara.loftus@intel.com> wrote:
> > Subject: [PATCH v3] net/iavf: fix VLAN offload strip flag
> >
> > For i40e kernel drivers which support either vlan(v1) or vlan(v2)
> > VIRTCHNL OP,it will set strip on when setting filter on. But dpdk
> > side will not change strip flag. To be consistent with dpdk side,
> > explicitly disable strip again.
> >
> > Bugzilla ID:1725
> > Cc: stable@dpdk.org
> >
> > v3:
> > - Fixed the vlan(v2) scenario by calling appropriate api
> > - Addresses Bugzilla ID: 1735
> > v2:
> > - Fixed indentation in commit message
> >
> > Signed-off-by: Amiya Ranjan Mohakud <amiyaranjan.mohakud@gmail.com>
>
> Hi Amiya,
>
> Thanks for the patch.
> Since your first patch was already merged into the main branch, this patch
> is considered a new patch (v1).
> If you submit another revision, it should be labelled v2.
>
> Since it's a new patch, it needs a new commit message. Something like:
>
> net/iavf: fix VLAN strip disabling for v2 capability
>
> Ensure the correct virtchnl op is called for disabling vlan stripping by
> checking if the device supports either v1 or v2 vlan capability and
> choosing the op accordingly.
>
> You should include the below line in the commit message which indicates it
> is a fix for the first patch:
> Fixes: 3bfad066f9b4 ("net/iavf: fix VLAN strip setting after enabling
> filter")
>
> Thanks,
> Ciara
>
> > ---
> > drivers/net/intel/iavf/iavf_ethdev.c | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/intel/iavf/iavf_ethdev.c
> > b/drivers/net/intel/iavf/iavf_ethdev.c
> > index c33fdd9069..335a8126c4 100644
> > --- a/drivers/net/intel/iavf/iavf_ethdev.c
> > +++ b/drivers/net/intel/iavf/iavf_ethdev.c
> > @@ -1388,6 +1388,7 @@ iavf_disable_vlan_strip_ex(struct rte_eth_dev
> > *dev, int on)
> > */
> > struct iavf_adapter *adapter =
> > IAVF_DEV_PRIVATE_TO_ADAPTER(dev->data->dev_private);
> > + struct iavf_info *vf = IAVF_DEV_PRIVATE_TO_VF(adapter);
> > struct rte_eth_conf *dev_conf = &dev->data->dev_conf;
> > int err;
> >
> > @@ -1395,7 +1396,10 @@ iavf_disable_vlan_strip_ex(struct rte_eth_dev
> > *dev, int on)
> > adapter->hw.mac.type == IAVF_MAC_VF ||
> > adapter->hw.mac.type == IAVF_MAC_X722_VF) {
> > if (on && !(dev_conf->rxmode.offloads &
> > RTE_ETH_RX_OFFLOAD_VLAN_STRIP)) {
> > - err = iavf_disable_vlan_strip(adapter);
> > + if (vf->vf_res->vf_cap_flags &
> > VIRTCHNL_VF_OFFLOAD_VLAN_V2)
> > + err = iavf_config_vlan_strip_v2(adapter,
> false);
> > + else
> > + err = iavf_disable_vlan_strip(adapter);
> > if (err)
> > return -EIO;
> > }
> > --
> > 2.39.5 (Apple Git-154)
>
>
[-- Attachment #2: Type: text/html, Size: 4579 bytes --]
prev parent reply other threads:[~2025-07-03 8:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 1:56 [PATCH] " Amiya Ranjan Mohakud
2025-06-23 10:57 ` Loftus, Ciara
2025-06-23 18:11 ` [PATCH v2] " Amiya Ranjan Mohakud
2025-06-23 18:50 ` Amiya Ranjan Mohakud
2025-06-24 9:19 ` Loftus, Ciara
2025-06-24 15:29 ` Amiya Ranjan Mohakud
2025-06-25 14:01 ` Loftus, Ciara
2025-06-25 16:00 ` Bruce Richardson
2025-06-26 3:34 ` Amiya Ranjan Mohakud
2025-06-26 4:34 ` Amiya Ranjan Mohakud
2025-06-24 9:19 ` Loftus, Ciara
2025-07-02 18:15 ` [PATCH] " Amiya Ranjan Mohakud
2025-07-02 18:22 ` [PATCH v3] " Amiya Ranjan Mohakud
2025-07-02 18:38 ` Amiya Ranjan Mohakud
2025-07-03 8:17 ` Loftus, Ciara
2025-07-03 8:25 ` Amiya Ranjan Mohakud [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=CAL+mCpPA5c6yVg4OhSFH2a5ymp11b7go+SnqP-rgh4gYBCK2uw@mail.gmail.com \
--to=amiyaranjan.mohakud@gmail.com \
--cc=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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).