From: Yury Norov <yury.norov@gmail.com>
To: Shradha Gupta <shradhagupta@linux.microsoft.com>
Cc: linux-hyperv@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, "Nipun Gupta" <nipun.gupta@amd.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Jonathan Cameron" <Jonathan.Cameron@huwei.com>,
"Anna-Maria Behnsen" <anna-maria@linutronix.de>,
"Kevin Tian" <kevin.tian@intel.com>,
"Long Li" <longli@microsoft.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Rob Herring" <robh@kernel.org>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Dexuan Cui" <decui@microsoft.com>,
"Wei Liu" <wei.liu@kernel.org>,
"Haiyang Zhang" <haiyangz@microsoft.com>,
"K. Y. Srinivasan" <kys@microsoft.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Konstantin Taranov" <kotaranov@microsoft.com>,
"Simon Horman" <horms@kernel.org>,
"Leon Romanovsky" <leon@kernel.org>,
"Maxim Levitsky" <mlevitsk@redhat.com>,
"Erni Sri Satya Vennela" <ernis@linux.microsoft.com>,
"Peter Zijlstra" <peterz@infradead.org>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
"Paul Rosswurm" <paulros@microsoft.com>,
"Shradha Gupta" <shradhagupta@microsoft.com>
Subject: Re: [PATCH v2 3/3] net: mana: Allocate MSI-X vectors dynamically as required
Date: Mon, 28 Apr 2025 09:38:06 -0400 [thread overview]
Message-ID: <aA-Evojnzt2z0RdH@yury> (raw)
In-Reply-To: <1745578478-15195-1-git-send-email-shradhagupta@linux.microsoft.com>
On Fri, Apr 25, 2025 at 03:54:38AM -0700, Shradha Gupta wrote:
> Currently, the MANA driver allocates MSI-X vectors statically based on
> MANA_MAX_NUM_QUEUES and num_online_cpus() values and in some cases ends
> up allocating more vectors than it needs. This is because, by this time
> we do not have a HW channel and do not know how many IRQs should be
> allocated.
>
> To avoid this, we allocate 1 MSI-X vector during the creation of HWC and
> after getting the value supported by hardware, dynamically add the
> remaining MSI-X vectors.
>
> Signed-off-by: Shradha Gupta <shradhagupta@linux.microsoft.com>
> Reviewed-by: Haiyang Zhang <haiyangz@microsoft.com>
> ---
> Changes in v2:
> * Use string 'MSI-X vectors' instead of 'pci vectors'
> * make skip-cpu a bool instead of int
> * rearrange the comment arout skip_cpu variable appropriately
> * update the capability bit for driver indicating dynamic IRQ allocation
> * enforced max line length to 80
> * enforced RCT convention
> * initialized gic to NULL, for when there is a possibility of gic
> not being populated correctly
> ---
> .../net/ethernet/microsoft/mana/gdma_main.c | 323 ++++++++++++++----
> include/net/mana/gdma.h | 11 +-
> 2 files changed, 269 insertions(+), 65 deletions(-)
To me, this patch looks too big, and it doesn't look like it does
exactly one thing.
Can you split it to a few small more reviewable chunks? For example,
I authored irq_setup() helper. If you split its rework and make it
a small preparation patch, I'll be able to add my review tag.
Thanks,
Yury
next prev parent reply other threads:[~2025-04-28 13:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 10:53 [PATCH v2 0/3] Allow dyn MSI-X vector allocation of MANA Shradha Gupta
2025-04-25 10:53 ` [PATCH v2 1/3] PCI: Export pci_msix_prepare_desc() for dynamic MSI-X alloc Shradha Gupta
2025-04-25 16:37 ` Bjorn Helgaas
2025-04-28 5:22 ` Shradha Gupta
2025-04-28 12:22 ` Thomas Gleixner
2025-04-29 8:43 ` Shradha Gupta
2025-04-25 10:54 ` [PATCH v2 2/3] PCI: hv: Allow dynamic MSI-X vector allocation Shradha Gupta
2025-04-28 13:47 ` Michael Kelley
2025-04-29 8:46 ` Shradha Gupta
2025-04-25 10:54 ` [PATCH v2 3/3] net: mana: Allocate MSI-X vectors dynamically as required Shradha Gupta
2025-04-25 16:35 ` Jakub Kicinski
2025-04-28 4:01 ` Shradha Gupta
2025-04-28 13:38 ` Yury Norov [this message]
2025-04-29 8:51 ` Shradha Gupta
2025-05-01 5:27 ` Michael Kelley
2025-05-01 14:23 ` Shradha Gupta
2025-05-01 15:56 ` Michael Kelley
2025-05-02 6:08 ` Shradha Gupta
2025-05-06 8:49 ` Shradha Gupta
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=aA-Evojnzt2z0RdH@yury \
--to=yury.norov@gmail.com \
--cc=Jonathan.Cameron@huwei.com \
--cc=andrew+netdev@lunn.ch \
--cc=anna-maria@linutronix.de \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=ernis@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=horms@kernel.org \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kw@linux.com \
--cc=kys@microsoft.com \
--cc=leon@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=lpieralisi@kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mlevitsk@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nipun.gupta@amd.com \
--cc=pabeni@redhat.com \
--cc=paulros@microsoft.com \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=shradhagupta@linux.microsoft.com \
--cc=shradhagupta@microsoft.com \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.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;
as well as URLs for NNTP newsgroup(s).