All of lore.kernel.org
 help / color / mirror / Atom feed
* Can we remove the logic of preventing MSI irq storms
@ 2011-07-14  6:43 Haitao Shan
  2011-07-14  7:06 ` Keir Fraser
  0 siblings, 1 reply; 2+ messages in thread
From: Haitao Shan @ 2011-07-14  6:43 UTC (permalink / raw)
  To: Keir Fraser; +Cc: xen-devel

Hi, Keir,

As you may remember (see c/s 17960), Xen implemented the logic of
preventing MSI irq storms. The reason of the IRQ storm at that time is
still unknown. But the logic is definitely needed at that time since
that NIC is the only device at my hand to test MSI.
The idea is simple: mask the second MSI interrupt when the first one
is still in processing. For HVM guests, we hooked at guest EOI write
to determime whether the first MSI is serviced already.

However, recently we find the logic has negative impact on 10G NIC
performance (assigned to guest). The logic lowers the interrupt
frequency that Xen can handle. It is a problem when the device is
generating too many interrupts as seen in this 10G NIC.

And now there is IRQ rate limit logic in Xenm which can also help to
prevent IRQ storms.

Given all the above, do you think it is time to remove the logic of
preventing MSI IRQ storm?

Shan Haitao

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Can we remove the logic of preventing MSI irq storms
  2011-07-14  6:43 Can we remove the logic of preventing MSI irq storms Haitao Shan
@ 2011-07-14  7:06 ` Keir Fraser
  0 siblings, 0 replies; 2+ messages in thread
From: Keir Fraser @ 2011-07-14  7:06 UTC (permalink / raw)
  To: Haitao Shan; +Cc: xen-devel

On 14/07/2011 07:43, "Haitao Shan" <maillists.shan@gmail.com> wrote:

> Hi, Keir,
> 
> As you may remember (see c/s 17960), Xen implemented the logic of
> preventing MSI irq storms. The reason of the IRQ storm at that time is
> still unknown. But the logic is definitely needed at that time since
> that NIC is the only device at my hand to test MSI.
> The idea is simple: mask the second MSI interrupt when the first one
> is still in processing. For HVM guests, we hooked at guest EOI write
> to determime whether the first MSI is serviced already.
> 
> However, recently we find the logic has negative impact on 10G NIC
> performance (assigned to guest). The logic lowers the interrupt
> frequency that Xen can handle. It is a problem when the device is
> generating too many interrupts as seen in this 10G NIC.
> 
> And now there is IRQ rate limit logic in Xenm which can also help to
> prevent IRQ storms.
> 
> Given all the above, do you think it is time to remove the logic of
> preventing MSI IRQ storm?

I'd be happy to see it go.

 -- Keir

> Shan Haitao

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-07-14  7:06 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-14  6:43 Can we remove the logic of preventing MSI irq storms Haitao Shan
2011-07-14  7:06 ` Keir Fraser

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.