From: Ahmed Zaki <ahmed.zaki@intel.com>
To: Petr Oros <poros@redhat.com>, <netdev@vger.kernel.org>
Cc: ivecera@redhat.com, jesse.brandeburg@intel.com,
linux-kernel@vger.kernel.org, edumazet@google.com,
anthony.l.nguyen@intel.com, kuba@kernel.org,
intel-wired-lan@lists.osuosl.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH net 2/2] iavf: schedule a request immediately after add/delete vlan
Date: Wed, 6 Sep 2023 09:33:25 -0600 [thread overview]
Message-ID: <b894c33a-2fc7-7049-4d7b-2a6ca06439d1@intel.com> (raw)
In-Reply-To: <20230906141411.121142-2-poros@redhat.com>
On 2023-09-06 08:14, Petr Oros wrote:
> When the iavf driver wants to reconfigure the VLAN filters
> (iavf_add_vlan, iavf_del_vlan), it sets a flag in
> aq_required:
> adapter->aq_required |= IAVF_FLAG_AQ_ADD_VLAN_FILTER;
> or:
> adapter->aq_required |= IAVF_FLAG_AQ_DEL_VLAN_FILTER;
>
> This is later processed by the watchdog_task, but it runs periodically
> every 2 seconds, so it can be a long time before it processes the request.
>
> In the worst case, the interface is unable to receive traffic for more
> than 2 seconds for no objective reason.
>
> Signed-off-by: Petr Oros <poros@redhat.com>
> Co-developed-by: Michal Schmidt <mschmidt@redhat.com>
> Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
> Co-developed-by: Ivan Vecera <ivecera@redhat.com>
> Signed-off-by: Ivan Vecera <ivecera@redhat.com>
> ---
> drivers/net/ethernet/intel/iavf/iavf_main.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/iavf/iavf_main.c b/drivers/net/ethernet/intel/iavf/iavf_main.c
> index 86d472dfdbc10c..d9f8ac1d57fd62 100644
> --- a/drivers/net/ethernet/intel/iavf/iavf_main.c
> +++ b/drivers/net/ethernet/intel/iavf/iavf_main.c
> @@ -821,7 +821,7 @@ iavf_vlan_filter *iavf_add_vlan(struct iavf_adapter *adapter,
> list_add_tail(&f->list, &adapter->vlan_filter_list);
> f->state = IAVF_VLAN_ADD;
> adapter->num_vlan_filters++;
> - adapter->aq_required |= IAVF_FLAG_AQ_ADD_VLAN_FILTER;
> + iavf_schedule_aq_request(adapter, IAVF_FLAG_AQ_ADD_VLAN_FILTER);
> }
>
> clearout:
> @@ -843,7 +843,7 @@ static void iavf_del_vlan(struct iavf_adapter *adapter, struct iavf_vlan vlan)
> f = iavf_find_vlan(adapter, vlan);
> if (f) {
> f->state = IAVF_VLAN_REMOVE;
> - adapter->aq_required |= IAVF_FLAG_AQ_DEL_VLAN_FILTER;
> + iavf_schedule_aq_request(adapter, IAVF_FLAG_AQ_DEL_VLAN_FILTER);
> }
>
> spin_unlock_bh(&adapter->mac_vlan_list_lock);
Reviewed-by: Ahmed Zaki <ahmed.zaki@intel.com>
Thanks.
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-09-06 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 14:14 [Intel-wired-lan] [PATCH net 1/2] iavf: add iavf_schedule_aq_request() helper Petr Oros
2023-09-06 14:14 ` [Intel-wired-lan] [PATCH net 2/2] iavf: schedule a request immediately after add/delete vlan Petr Oros
2023-09-06 15:33 ` Ahmed Zaki [this message]
2023-09-06 15:32 ` [Intel-wired-lan] [PATCH net 1/2] iavf: add iavf_schedule_aq_request() helper Ahmed Zaki
2023-09-06 16:44 ` Simon Horman
2023-09-07 7:01 ` Petr Oros
2023-09-07 12:42 ` Ahmed Zaki
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=b894c33a-2fc7-7049-4d7b-2a6ca06439d1@intel.com \
--to=ahmed.zaki@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=poros@redhat.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