From: patchwork-bot+netdevbpf@kernel.org
To: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com, netdev@vger.kernel.org,
piotr.raczynski@intel.com
Subject: Re: [PATCH net-next v2 0/8][pull request] ice: support dynamic interrupt allocation
Date: Wed, 17 May 2023 08:30:23 +0000 [thread overview]
Message-ID: <168431222334.29655.6434690104586042687.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230516174021.2707029-1-anthony.l.nguyen@intel.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Tony Nguyen <anthony.l.nguyen@intel.com>:
On Tue, 16 May 2023 10:40:13 -0700 you wrote:
> Piotr Raczynski says:
>
> This patchset reimplements MSIX interrupt allocation logic to allow dynamic
> interrupt allocation after MSIX has been initially enabled. This allows
> current and future features to allocate and free interrupts as needed and
> will help to drastically decrease number of initially preallocated
> interrupts (even down to the API hard limit of 1). Although this patchset
> does not change behavior in terms of actual number of allocated interrupts
> during probe, it will be subject to change.
>
> [...]
Here is the summary with links:
- [net-next,v2,1/8] ice: move interrupt related code to separate file
https://git.kernel.org/netdev/net-next/c/38e97a98e371
- [net-next,v2,2/8] ice: use pci_irq_vector helper function
https://git.kernel.org/netdev/net-next/c/afe87cfe820e
- [net-next,v2,3/8] ice: use preferred MSIX allocation api
https://git.kernel.org/netdev/net-next/c/05018936a1fe
- [net-next,v2,4/8] ice: refactor VF control VSI interrupt handling
https://git.kernel.org/netdev/net-next/c/369bb5a2a9a7
- [net-next,v2,5/8] ice: remove redundant SRIOV code
https://git.kernel.org/netdev/net-next/c/524012c69ee1
- [net-next,v2,6/8] ice: add individual interrupt allocation
https://git.kernel.org/netdev/net-next/c/4aad5335969f
- [net-next,v2,7/8] ice: track interrupt vectors with xarray
https://git.kernel.org/netdev/net-next/c/cfebc0a36ea5
- [net-next,v2,8/8] ice: add dynamic interrupt allocation
https://git.kernel.org/netdev/net-next/c/011670cc340c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-05-17 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 17:40 [PATCH net-next v2 0/8][pull request] ice: support dynamic interrupt allocation Tony Nguyen
2023-05-16 17:40 ` [PATCH net-next v2 1/8] ice: move interrupt related code to separate file Tony Nguyen
2023-05-16 17:40 ` [PATCH net-next v2 2/8] ice: use pci_irq_vector helper function Tony Nguyen
2023-05-16 17:40 ` [PATCH net-next v2 3/8] ice: use preferred MSIX allocation api Tony Nguyen
2023-05-16 17:40 ` [PATCH net-next v2 4/8] ice: refactor VF control VSI interrupt handling Tony Nguyen
2023-05-16 17:40 ` [PATCH net-next v2 5/8] ice: remove redundant SRIOV code Tony Nguyen
2023-05-16 17:40 ` [PATCH net-next v2 6/8] ice: add individual interrupt allocation Tony Nguyen
2023-05-16 17:40 ` [PATCH net-next v2 7/8] ice: track interrupt vectors with xarray Tony Nguyen
2023-05-16 17:40 ` [PATCH net-next v2 8/8] ice: add dynamic interrupt allocation Tony Nguyen
2023-05-17 8:30 ` patchwork-bot+netdevbpf [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=168431222334.29655.6434690104586042687.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=piotr.raczynski@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.