From: Jeff Garzik <jgarzik@pobox.com>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Bjorn Helgaas <bhelgaas@google.com>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Yinghai Lu <yinghai@kernel.org>,
Matthew Wilcox <willy@linux.intel.com>,
x86@kernel.org, linux-pci@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [PATCH 0/5] x86, MSI, AHCI: Support multiple MSIs
Date: Thu, 16 Aug 2012 12:19:43 -0400 [thread overview]
Message-ID: <502D1D9F.9020203@pobox.com> (raw)
In-Reply-To: <cover.1345124063.git.agordeev@redhat.com>
On 08/16/2012 10:45 AM, Alexander Gordeev wrote:
> Currently multiple MSI mode is limited to a single vector per device (at
> least on x86 and PPC). This series breathes life into pci_enable_msi_block()
> and makes it possible to set interrupt affinity for multiple IRQs, similarly
> to MSI-X. Yet, only for x86 and only when IOMMUs are present.
>
> Although IRQ and PCI subsystems are modified, the current behaviour left
> intact. The drivers could just start using multiple MSIs just by following
> the existing documentation.
>
> The AHCI device driver makes use of the new mode and a new function -
> pci_enable_msi_block_auto() - patches 4,5.
>
> The series is adapted to Ingo's -tip repository, x86/apic branch.
> Patches 4,5 could be applied independently of patches 1-3.
>
> Attached patches:
> 1/5 x86, MSI: Support multiple MSIs in presense of IRQ remapping
> 2/5 x86, MSI: Allocate as many multiple IRQs as requested
> 3/5 x86, MSI: Minor readability fixes
> 4/5 PCI, MSI: Enable multiple MSIs with pci_enable_msi_block_auto()
> 5/5 AHCI: Support multiple MSIs
Numbers? I would like to see measurements that show this is a benefit.
I'm especially wondering about lock contention for the case of
multiple, fast devices (e.g. RAM over SATA, or PCIe flash).
Because I see the following obvious problems immediately:
1) AHCI takes a host-wide lock during interrupt processing, which quite
reduces the value of "interrupts generated by different
ports could be serviced on different CPUs"
2) We do not put AHCI-specific code in libata-core. Try libahci.c or
ahci.c.
Regards,
Jeff
next prev parent reply other threads:[~2012-08-16 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 14:45 [PATCH 0/5] x86, MSI, AHCI: Support multiple MSIs Alexander Gordeev
2012-08-16 14:46 ` [PATCH 1/5] x86, MSI: Support multiple MSIs in presense of IRQ remapping Alexander Gordeev
2012-08-16 14:47 ` [PATCH 2/5] x86, MSI: Allocate as many multiple IRQs as requested Alexander Gordeev
2012-08-16 14:48 ` [PATCH 3/5] x86, MSI: Minor readability fixes Alexander Gordeev
2012-08-16 14:49 ` [PATCH 4/5] PCI, MSI: Enable multiple MSIs with pci_enable_msi_block_auto() Alexander Gordeev
2012-08-16 16:00 ` Bjorn Helgaas
2012-08-17 8:19 ` Alexander Gordeev
2012-08-17 14:22 ` Bjorn Helgaas
2012-08-16 14:49 ` [PATCH 5/5] AHCI: Support multiple MSIs Alexander Gordeev
2012-08-16 16:19 ` Jeff Garzik [this message]
2012-08-17 8:30 ` [PATCH 0/5] x86, MSI, " Alexander Gordeev
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=502D1D9F.9020203@pobox.com \
--to=jgarzik@pobox.com \
--cc=agordeev@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
--cc=willy@linux.intel.com \
--cc=x86@kernel.org \
--cc=yinghai@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.