All of lore.kernel.org
 help / color / mirror / Atom feed
From: Megha Dey <megha.dey@intel.com>
To: bhelgaas@google.com, linux-pci@vger.kernel.org
Cc: ashok.raj@intel.com, jacob.jun.pan@linux.intel.com
Subject: Re: [RFC V1 0/6] Introduce dynamic allocation/freeing of MSI-X vectors
Date: Fri, 21 Jun 2019 17:23:38 -0700	[thread overview]
Message-ID: <1561163018.12836.1.camel@intel.com> (raw)
In-Reply-To: <1560981824-3966-1-git-send-email-megha.dey@linux.intel.com>

On Wed, 2019-06-19 at 15:03 -0700, Megha Dey wrote:
> Currently, MSI-X vector enabling and allocation for a PCIe device is
> static i.e. a device driver gets only one chance to enable a specific
> number of MSI-X vectors, usually during device probe. Also, in many
> cases, drivers usually reserve more than required number of vectors
> anticipating their use, which unnecessarily blocks resources that
> could have been made available to other devices. Lastly, there is no
> way for drivers to reserve more vectors, if the MSI-x has already
> been
> enabled for that device.
>  
> Hence, a dynamic MSI-X kernel infrastructure can benefit drivers by
> deferring MSI-X allocation to post probe phase, where actual demand
> information is available.
>  
> This patchset enables the dynamic allocation/de-allocation of MSI-X
> vectors by introducing 2 new APIs:
> pci_alloc_irq_vectors_dyn() and pci_free_irq_vectors_grp():
> 
> We have had requests from some of the NIC/RDMA users who have lots of
> interrupt resources and would like to allocate them on demand,
> instead of using an all or none approach.
> 
> The APIs are fairly well tested (multiple allocations/deallocations),
> but we have no early adopters yet. Hence, sending this series as an
> RFC for review and comments.
> 
> The patches are based out of Linux 5.2-rc5.

I have resent the patches to include LKML.
https://lkml.org/lkml/2019/6/21/923

> 
> Megha Dey (6):
>   PCI/MSI: New structures/macros for dynamic MSI-X allocation
>   PCI/MSI: Dynamic allocation of MSI-X vectors by group
>   x86: Introduce the dynamic teardown function
>   PCI/MSI: Introduce new structure to manage MSI-x entries
>   PCI/MSI: Free MSI-X resources by group
>   Documentation: PCI/MSI: Document dynamic MSI-X infrastructure
> 
>  Documentation/PCI/MSI-HOWTO.txt |  38 +++++
>  arch/x86/include/asm/x86_init.h |   1 +
>  arch/x86/kernel/x86_init.c      |   6 +
>  drivers/pci/msi.c               | 363
> +++++++++++++++++++++++++++++++++++++---
>  drivers/pci/probe.c             |   9 +
>  include/linux/device.h          |   3 +
>  include/linux/msi.h             |  13 ++
>  include/linux/pci.h             |  61 +++++++
>  kernel/irq/msi.c                |  34 +++-
>  9 files changed, 497 insertions(+), 31 deletions(-)
> 

      parent reply	other threads:[~2019-06-22  0:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19 22:03 [RFC V1 0/6] Introduce dynamic allocation/freeing of MSI-X vectors Megha Dey
2019-06-19 22:03 ` [RFC V1 1/6] PCI/MSI: New structures/macros for dynamic MSI-X allocation Megha Dey
2019-06-19 22:03 ` [RFC V1 2/6] PCI/MSI: Dynamic allocation of MSI-X vectors by group Megha Dey
2019-06-19 22:03 ` [RFC V1 3/6] x86: Introduce the dynamic teardown function Megha Dey
2019-06-19 22:03 ` [RFC V1 4/6] PCI/MSI: Introduce new structure to manage MSI-x entries Megha Dey
2019-06-19 22:03 ` [RFC V1 5/6] PCI/MSI: Free MSI-X resources by group Megha Dey
2019-06-19 22:03 ` [RFC V1 6/6] Documentation: PCI/MSI: Document dynamic MSI-X infrastructure Megha Dey
2019-06-22  0:23 ` Megha Dey [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=1561163018.12836.1.camel@intel.com \
    --to=megha.dey@intel.com \
    --cc=ashok.raj@intel.com \
    --cc=bhelgaas@google.com \
    --cc=jacob.jun.pan@linux.intel.com \
    --cc=linux-pci@vger.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 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.