From: David Su <david.w.su@intel.com>
To: linux-kernel@vger.kernel.org
Cc: bigeasy@linutronix.de, tglx@linutronix.de, rostedt@goodmis.org,
David Su <david.w.su@intel.com>
Subject: [PATCH RT] vfio-pci: Set MSI/MSI-X ISR to non-threaded
Date: Thu, 30 Nov 2017 17:05:35 -0800 [thread overview]
Message-ID: <1512090335-6888-1-git-send-email-david.w.su@intel.com> (raw)
Setting MSI/MSI-X ISR to be non-threaded will result in shorter and more
deterministic IRQ delivery latencies to VFIO applications, because
context switches to the ISR thread are eliminated. This is important
for applications with low latency requirement running in virtual
machines on RT Linux host with assigned devices through vfio-pci.
A FPGA based interrupt testing device was used to compare latencies with
threaded and non-threaded vfio-pci ISR. The device has a free running
time stamp counter and a register recording the time an interrupt was
sent to the host. With these registers the device driver and test
application for the device are able to calculate and record the latency
between the time an interrupt was sent and the time the ISR in the
device's driver was invoked.
The result is with non-threaded vfio-pci ISR the average latency is
reduced by about 54% and the maximum-minimum latency range is reduced by
about 65%.
Non-threaded vfio-pci ISR:
Minimum 4.18us, Average 4.47us, Maximum 10.26us
Threaded vfio-pci ISR:
Minimum 8.97us, Average 9.65us, Maximum 26.11us
Signed-off-by: David Su <david.w.su@intel.com>
---
drivers/vfio/pci/vfio_pci_intrs.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/vfio/pci/vfio_pci_intrs.c b/drivers/vfio/pci/vfio_pci_intrs.c
index 1c46045..4c54e56 100644
--- a/drivers/vfio/pci/vfio_pci_intrs.c
+++ b/drivers/vfio/pci/vfio_pci_intrs.c
@@ -333,7 +333,7 @@ static int vfio_msi_set_vector_signal(struct vfio_pci_device *vdev,
pci_write_msi_msg(irq, &msg);
}
- ret = request_irq(irq, vfio_msihandler, 0,
+ ret = request_irq(irq, vfio_msihandler, IRQF_NO_THREAD,
vdev->ctx[vector].name, trigger);
if (ret) {
kfree(vdev->ctx[vector].name);
--
1.7.0.4
next reply other threads:[~2017-12-01 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 1:05 David Su [this message]
2017-12-01 2:08 ` Steven Rostedt
2017-12-07 1:27 ` Su, David W
2017-12-07 8:52 ` Steven Rostedt
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=1512090335-6888-1-git-send-email-david.w.su@intel.com \
--to=david.w.su@intel.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®