From: Keith Busch <keith.busch@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
"Bauer, Scott" <scott.bauer@intel.com>,
"Derrick, Jonathan" <jonathan.derrick@intel.com>
Subject: Re: [PATCH] PCI/VMD: White list for fast interrupt handlers
Date: Wed, 9 May 2018 09:26:53 -0600 [thread overview]
Message-ID: <20180509152652.GA823@localhost.localdomain> (raw)
In-Reply-To: <20180509043828.GA9413@infradead.org>
On Tue, May 08, 2018 at 09:38:28PM -0700, Christoph Hellwig wrote:
> On Tue, May 08, 2018 at 10:00:22AM -0600, Keith Busch wrote:
> > Devices with slow interrupt handlers are significantly harming performance
> > when their interrupt vector is shared with a fast device. This patch
> > creates a class code white list for devices with known fast interrupt
> > handlers, and all other devices will share a single vector so they don't
> > interfere with performance.
> >
> > At the moment, only the NVM Express class code is on the list, but more
> > may be added if VMD users desire to use other low-latency devices in
> > these domains.
>
> I think this is far too much of a hack. Just don't use VMD if your
> care about performance.
I'm not aware of an easier way you can direct-assign an entire PCIe domain
to a virtual machine. :)
next prev parent reply other threads:[~2018-05-09 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 16:00 [PATCH] PCI/VMD: White list for fast interrupt handlers Keith Busch
2018-05-09 4:38 ` Christoph Hellwig
2018-05-09 15:26 ` Keith Busch [this message]
2018-05-11 15:39 ` Derrick, Jonathan
2018-05-25 19:11 ` Derrick, Jonathan
2018-06-28 11:22 ` Lorenzo Pieralisi
2018-06-28 14:02 ` Keith Busch
2018-06-28 16:32 ` Lorenzo Pieralisi
2018-05-14 14:15 ` Christoph Hellwig
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=20180509152652.GA823@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=bhelgaas@google.com \
--cc=hch@infradead.org \
--cc=jonathan.derrick@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=scott.bauer@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.