From: Nguyen, Anthony L <anthony.l.nguyen@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net v1] iavf: Fix limit of total number of queues to active queues of VF
Date: Tue, 31 Aug 2021 22:56:57 +0000 [thread overview]
Message-ID: <5a1a2e60f5e22ea807a142d057a28face0c82a1f.camel@intel.com> (raw)
In-Reply-To: <20210830090220.271120-1-karen.sornek@intel.com>
On Mon, 2021-08-30 at 11:02 +0200, Karen Sornek wrote:
> In the absence of this validation, if the user requests to
> configure queues more than the enabled queues, it results in
> sending the requested number of queues to the kernel stack
> (due to the asynchronous nature of VF response), in which
> case the stack might pick a queue to transmit that is not
> enabled and result in Tx hang. Fix this bug by
> limiting the total number of queues allocated for VF to
> active queues of VF.
>
> Fixes: 129cf89e5856 ("iavf: rename functions and structs to new
> name")
I believe this commit is more appropriate?
d5b33d024496 ("i40evf: add ndo_setup_tc callback to i40evf")
> Signed-off-by: Ashwin Vijayavel <ashwin.vijayavel@intel.com>
> Signed-off-by: Karen Sornek <karen.sornek@intel.com>
next prev parent reply other threads:[~2021-08-31 22:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 9:02 [Intel-wired-lan] [PATCH net v1] iavf: Fix limit of total number of queues to active queues of VF Karen Sornek
2021-08-30 8:49 ` [Intel-wired-lan] Incorrect time (was: [PATCH net v1] iavf: Fix limit of total number of queues to active queues of VF) Paul Menzel
2021-08-31 22:56 ` Nguyen, Anthony L [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-01 7:21 [Intel-wired-lan] [PATCH net v1] iavf: Fix limit of total number of queues to active queues of VF Karen Sornek
2021-12-14 14:16 ` Jankowski, Konrad0
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=5a1a2e60f5e22ea807a142d057a28face0c82a1f.camel@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@osuosl.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