From: Jan Kiszka <jan.kiszka@web.de>
To: Gleb Natapov <gleb@redhat.com>
Cc: Avi Kivity <avi@redhat.com>, kvm-devel <kvm@vger.kernel.org>
Subject: Re: assign-dev: Purpose of interrupt_work
Date: Mon, 12 Oct 2009 09:27:19 +0200 [thread overview]
Message-ID: <4AD2DA57.6030006@web.de> (raw)
In-Reply-To: <20091012071310.GT16702@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 620 bytes --]
Gleb Natapov wrote:
> On Mon, Oct 12, 2009 at 09:03:18AM +0200, Jan Kiszka wrote:
>> Hi,
>>
>> I was starring at the IRQ delivery path of assigned devices for a while,
>> wondering why we have a work queue there. Now, after looking at some
>> prehistoric versions, I think the reason is that there once was a mutex
>> involved while we now use RCU. Am I right that we could actually drop
>> this indirection today?
>>
> ioapic/pic path still has mutex. If MSIX is used (like it should) we can
> drop work queue.
I see. Wouldn't it be feasible to convert the fast paths of [io]apic to
spinlocks?
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-10-12 7:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 7:03 assign-dev: Purpose of interrupt_work Jan Kiszka
2009-10-12 7:13 ` Gleb Natapov
2009-10-12 7:27 ` Jan Kiszka [this message]
2009-10-12 7:45 ` Gleb Natapov
2009-10-12 7:50 ` Jan Kiszka
2009-10-12 7:57 ` Gleb Natapov
2009-10-12 8:16 ` Jan Kiszka
2009-10-12 8:39 ` Gleb Natapov
2009-10-12 9:04 ` Jan Kiszka
2009-10-12 9:14 ` Avi Kivity
2009-10-12 9:25 ` Jan Kiszka
2009-10-12 9:30 ` Avi Kivity
2009-10-12 9:38 ` Gleb Natapov
2009-10-12 9:40 ` Avi Kivity
2009-10-12 9:42 ` Gleb Natapov
2009-10-12 9:14 ` Gleb Natapov
2009-10-12 8:39 ` Avi Kivity
2009-10-12 9:05 ` Gleb Natapov
2009-10-12 9:07 ` Avi Kivity
2009-10-12 9:07 ` Jan Kiszka
2009-10-12 9:16 ` Avi Kivity
2009-10-12 17:36 ` Marcelo Tosatti
2009-10-12 20:44 ` Jan Kiszka
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=4AD2DA57.6030006@web.de \
--to=jan.kiszka@web.de \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@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.