Re: assign-dev: Purpose of interrupt_work

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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: signature.asc
Description: OpenPGP digital signature


[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux