From: Jakub Kicinski <kuba@kernel.org>
To: Piotr Raczynski <piotr.raczynski@intel.com>
Cc: michal.swiatkowski@intel.com, netdev@vger.kernel.org,
jesse.brandeburg@intel.com, intel-wired-lan@lists.osuosl.org,
shiraz.saleem@intel.com
Subject: Re: [Intel-wired-lan] [PATCH net-next v2 0/8] ice: support dynamic interrupt allocation
Date: Wed, 22 Mar 2023 12:37:06 -0700 [thread overview]
Message-ID: <20230322123706.4a787946@kernel.org> (raw)
In-Reply-To: <20230322162530.3317238-1-piotr.raczynski@intel.com>
On Wed, 22 Mar 2023 17:25:22 +0100 Piotr Raczynski wrote:
> 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.
Have you seen the mlx5 patch set? I haven't read in detail but seems
like you're working on the same stuff so could be worth cross-checking
each other's work:
https://lore.kernel.org/all/20230320175144.153187-1-saeed@kernel.org/
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Piotr Raczynski <piotr.raczynski@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
michal.swiatkowski@intel.com, shiraz.saleem@intel.com,
jacob.e.keller@intel.com, sridhar.samudrala@intel.com,
jesse.brandeburg@intel.com, aleksander.lobakin@intel.com,
lukasz.czapnik@intel.com
Subject: Re: [PATCH net-next v2 0/8] ice: support dynamic interrupt allocation
Date: Wed, 22 Mar 2023 12:37:06 -0700 [thread overview]
Message-ID: <20230322123706.4a787946@kernel.org> (raw)
In-Reply-To: <20230322162530.3317238-1-piotr.raczynski@intel.com>
On Wed, 22 Mar 2023 17:25:22 +0100 Piotr Raczynski wrote:
> 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.
Have you seen the mlx5 patch set? I haven't read in detail but seems
like you're working on the same stuff so could be worth cross-checking
each other's work:
https://lore.kernel.org/all/20230320175144.153187-1-saeed@kernel.org/
next prev parent reply other threads:[~2023-03-22 19:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-22 16:25 [Intel-wired-lan] [PATCH net-next v2 0/8] ice: support dynamic interrupt allocation Piotr Raczynski
2023-03-22 16:25 ` Piotr Raczynski
2023-03-22 16:25 ` [Intel-wired-lan] [PATCH net-next v2 1/8] ice: move interrupt related code to separate file Piotr Raczynski
2023-03-22 16:25 ` Piotr Raczynski
2023-03-22 16:25 ` [Intel-wired-lan] [PATCH net-next v2 2/8] ice: use pci_irq_vector helper function Piotr Raczynski
2023-03-22 16:25 ` Piotr Raczynski
2023-03-22 16:25 ` [Intel-wired-lan] [PATCH net-next v2 3/8] ice: use preferred MSIX allocation api Piotr Raczynski
2023-03-22 16:25 ` Piotr Raczynski
2023-03-22 16:25 ` [Intel-wired-lan] [PATCH net-next v2 4/8] ice: refactor VF control VSI interrupt handling Piotr Raczynski
2023-03-22 16:25 ` Piotr Raczynski
2023-03-22 16:25 ` [Intel-wired-lan] [PATCH net-next v2 5/8] ice: remove redundant SRIOV code Piotr Raczynski
2023-03-22 16:25 ` Piotr Raczynski
2023-03-22 16:25 ` [Intel-wired-lan] [PATCH net-next v2 6/8] ice: add individual interrupt allocation Piotr Raczynski
2023-03-22 16:25 ` Piotr Raczynski
2023-03-22 16:25 ` [Intel-wired-lan] [PATCH net-next v2 7/8] ice: track interrupt vectors with xarray Piotr Raczynski
2023-03-22 16:25 ` Piotr Raczynski
2023-03-22 16:25 ` [Intel-wired-lan] [PATCH net-next v2 8/8] ice: add dynamic interrupt allocation Piotr Raczynski
2023-03-22 16:25 ` Piotr Raczynski
2023-03-22 17:33 ` [Intel-wired-lan] [PATCH net-next v2 0/8] ice: support " Jacob Keller
2023-03-22 17:33 ` Jacob Keller
2023-03-22 18:40 ` [Intel-wired-lan] " Piotr Raczynski
2023-03-22 18:40 ` Piotr Raczynski
2023-03-22 19:03 ` [Intel-wired-lan] " Keller, Jacob E
2023-03-22 19:03 ` Keller, Jacob E
2023-03-22 19:37 ` Jakub Kicinski [this message]
2023-03-22 19:37 ` Jakub Kicinski
2023-03-22 20:05 ` [Intel-wired-lan] " Jacob Keller
2023-03-22 20:05 ` Jacob Keller
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=20230322123706.4a787946@kernel.org \
--to=kuba@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=michal.swiatkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=piotr.raczynski@intel.com \
--cc=shiraz.saleem@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.