From: Simon Horman <horms@kernel.org>
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>,
Yury Norov <yury.norov@gmail.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???~Dski <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>,
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 v4 0/5] Allow dyn MSI-X vector allocation of MANA
Date: Fri, 30 May 2025 19:07:32 +0100 [thread overview]
Message-ID: <20250530180732.GS1484967@horms.kernel.org> (raw)
In-Reply-To: <20250529132845.GE27681@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
On Thu, May 29, 2025 at 06:28:45AM -0700, Shradha Gupta wrote:
> On Wed, May 28, 2025 at 07:55:08PM +0100, Simon Horman wrote:
> > On Tue, May 27, 2025 at 08:57:33AM -0700, Shradha Gupta wrote:
> > > In this patchset we want to enable the MANA driver to be able to
> > > allocate MSI-X vectors in PCI dynamically.
> > >
> > > The first patch exports pci_msix_prepare_desc() in PCI to be able to
> > > correctly prepare descriptors for dynamically added MSI-X vectors.
> > >
> > > The second patch adds the support of dynamic vector allocation in
> > > pci-hyperv PCI controller by enabling the MSI_FLAG_PCI_MSIX_ALLOC_DYN
> > > flag and using the pci_msix_prepare_desc() exported in first patch.
> > >
> > > The third patch adds a detailed description of the irq_setup(), to
> > > help understand the function design better.
> > >
> > > The fourth patch is a preparation patch for mana changes to support
> > > dynamic IRQ allocation. It contains changes in irq_setup() to allow
> > > skipping first sibling CPU sets, in case certain IRQs are already
> > > affinitized to them.
> > >
> > > The fifth patch has the changes in MANA driver to be able to allocate
> > > MSI-X vectors dynamically. If the support does not exist it defaults to
> > > older behavior.
> >
> > Hi Shradha,
> >
> > It's unclear what the target tree for this patch-set is.
> > But if it is net-next, which seems likely given the code under
> > drivers/net/, then:
> >
> > Please include that target in the subject of each patch in the patch-set.
> >
> > Subject: [PATCH v5 net-next 0/5] ...
> >
> > And, moreover, ...
> >
> > ## Form letter - net-next-closed
> >
> > The merge window for v6.16 has begun and therefore net-next is closed
> > for new drivers, features, code refactoring and optimizations. We are
> > currently accepting bug fixes only.
> >
> > Please repost when net-next reopens after June 8th.
> >
> > RFC patches sent for review only are obviously welcome at any time.
>
> Thank you Simon.
>
> While posting this patchset I was a bit confused about what should be
> the target tree. That's why in the cover letter of the V1 for this
> series, I had requested more clarity on the same (since there are patches
> from PCI and net-next both).
>
> In such cases how do we decide which tree to target?
Yes, that isn't entirely clear to me either.
Hopefully the maintainers can negotiate this.
>
> Also, noted about the next merge window for net-next :-)
>
> Regards,
> Shradha.
>
next prev parent reply other threads:[~2025-05-30 18:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 15:57 [PATCH v4 0/5] Allow dyn MSI-X vector allocation of MANA Shradha Gupta
2025-05-27 15:57 ` [PATCH v4 1/5] PCI/MSI: Export pci_msix_prepare_desc() for dynamic MSI-X allocations Shradha Gupta
2025-05-29 3:46 ` Saurabh Singh Sengar
2025-05-27 15:58 ` [PATCH v4 2/5] PCI: hv: Allow dynamic MSI-X vector allocation Shradha Gupta
2025-05-29 3:46 ` Saurabh Singh Sengar
2025-05-27 15:58 ` [PATCH v4 3/5] net: mana: explain irq_setup() algorithm Shradha Gupta
2025-05-27 19:10 ` Yury Norov
2025-05-29 13:15 ` Shradha Gupta
2025-05-27 15:58 ` [PATCH v4 4/5] net: mana: Allow irq_setup() to skip cpus for affinity Shradha Gupta
2025-05-27 15:59 ` [PATCH v4 5/5] net: mana: Allocate MSI-X vectors dynamically Shradha Gupta
2025-05-28 8:16 ` Saurabh Singh Sengar
2025-05-29 13:17 ` Shradha Gupta
2025-05-28 18:52 ` Simon Horman
2025-05-29 13:18 ` Shradha Gupta
2025-05-29 3:45 ` Saurabh Singh Sengar
2025-05-29 13:20 ` Shradha Gupta
2025-05-28 18:55 ` [PATCH v4 0/5] Allow dyn MSI-X vector allocation of MANA Simon Horman
2025-05-29 13:28 ` Shradha Gupta
2025-05-30 18:07 ` Simon Horman [this message]
2025-06-03 4:15 ` Shradha Gupta
2025-06-01 14:53 ` Zhu Yanjun
2025-06-03 4:17 ` 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=20250530180732.GS1484967@horms.kernel.org \
--to=horms@kernel.org \
--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=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 \
--cc=yury.norov@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox