From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next 0/3] refactor irq allocation in ice
Date: Tue, 26 Apr 2022 17:24:00 -0700 [thread overview]
Message-ID: <c149bf88-f63e-667d-6a00-cafd962018b4@intel.com> (raw)
In-Reply-To: <20211222062201.36302-1-michal.swiatkowski@linux.intel.com>
On 12/21/2021 10:21 PM, Michal Swiatkowski wrote:
> The ice driver uses the old PCI irq reseveration API. Change the ice
> driver to use the current API.
>
> Implement a fallback mechanism where, if the driver can't reserve the
> maximum number of interrupts, it will limit the number of queues or
> disable capabilities.
A very similar implementation was already rejected by netdev [1]. I
believe there's kernel work being done for dynamic MSIX allocations
which is the route we should look to take on this (when it's completed).
Thanks,
Tony
[1]
https://lore.kernel.org/netdev/20210113234226.3638426-1-anthony.l.nguyen at intel.com/
prev parent reply other threads:[~2022-04-27 0:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 6:21 [Intel-wired-lan] [PATCH net-next 0/3] refactor irq allocation in ice Michal Swiatkowski
2021-12-22 6:21 ` [Intel-wired-lan] [PATCH net-next 1/3] ice: add check for eswitch support Michal Swiatkowski
2021-12-22 6:22 ` [Intel-wired-lan] [PATCH net-next 2/3] ice: change mode only if eswitch is supported Michal Swiatkowski
2021-12-22 6:22 ` [Intel-wired-lan] [PATCH net-next 3/3] ice: use new alloc irqs API Michal Swiatkowski
2021-12-22 16:33 ` [Intel-wired-lan] [PATCH net-next 0/3] refactor irq allocation in ice Jonathan Toppins
2022-04-27 0:24 ` Tony Nguyen [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=c149bf88-f63e-667d-6a00-cafd962018b4@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