From: "Jankowski, Konrad0" <konrad0.jankowski@intel.com>
To: "Jagielski, Jedrzej" <jedrzej.jagielski@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Cc: "Patynowski, PrzemyslawX" <przemyslawx.patynowski@intel.com>,
"Jagielski, Jedrzej" <jedrzej.jagielski@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net v1] iavf: Fix VLAN_V2 addition/rejection
Date: Mon, 27 Jun 2022 11:03:30 +0000 [thread overview]
Message-ID: <DM8PR11MB5621890968560ABDDEFE1817ABB99@DM8PR11MB5621.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220610121554.3047245-1-jedrzej.jagielski@intel.com>
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
> Jedrzej Jagielski
> Sent: Friday, June 10, 2022 2:16 PM
> To: intel-wired-lan@lists.osuosl.org
> Cc: Patynowski, PrzemyslawX <przemyslawx.patynowski@intel.com>;
> Jagielski, Jedrzej <jedrzej.jagielski@intel.com>
> Subject: [Intel-wired-lan] [PATCH net v1] iavf: Fix VLAN_V2
> addition/rejection
>
> From: Przemyslaw Patynowski <przemyslawx.patynowski@intel.com>
>
> Fix VLAN addition, so that PF driver does not reject whole VLAN batch.
> Add VLAN reject handling, so rejected VLANs, won't litter VLAN filter list. Fix
> handling of active_(c/s)vlans, so it will be possible to re-add VLAN filters for
> user.
> Without this patch, after changing trust to off, with VLAN filters saturated, no
> VLAN is added, due to PF rejecting addition.
>
> Fixes: 92fc50859872 ("iavf: Restrict maximum VLAN filters for
> VIRTCHNL_VF_OFFLOAD_VLAN_V2")
> Signed-off-by: Przemyslaw Patynowski
> <przemyslawx.patynowski@intel.com>
> Signed-off-by: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
> ---
> drivers/net/ethernet/intel/iavf/iavf.h | 9 ++-
> drivers/net/ethernet/intel/iavf/iavf_main.c | 10 ++-
> .../net/ethernet/intel/iavf/iavf_virtchnl.c | 65 ++++++++++++++++++-
> 3 files changed, 74 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/iavf/iavf.h
> b/drivers/net/ethernet/intel/iavf/iavf.h
> index 49aed3e506a6..86bc61c300a7 100644
> --- a/drivers/net/ethernet/intel/iavf/iavf.h
> +++ b/drivers/net/ethernet/intel/iavf/iavf.h
> @@ -159,8 +159,12 @@ struct iavf_vlan {
Tested-by: Konrad Jankowski <konrad0.jankowski@intel.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2022-06-27 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 12:15 [Intel-wired-lan] [PATCH net v1] iavf: Fix VLAN_V2 addition/rejection Jedrzej Jagielski
2022-06-27 11:03 ` Jankowski, Konrad0 [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=DM8PR11MB5621890968560ABDDEFE1817ABB99@DM8PR11MB5621.namprd11.prod.outlook.com \
--to=konrad0.jankowski@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jedrzej.jagielski@intel.com \
--cc=przemyslawx.patynowski@intel.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).