All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.xen@gmail.com>
To: Haitao Shan <maillists.shan@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Can we remove the logic of preventing MSI irq storms
Date: Thu, 14 Jul 2011 08:06:59 +0100	[thread overview]
Message-ID: <CA445423.1DD69%keir.xen@gmail.com> (raw)
In-Reply-To: <CAFQ2Z+f6qfWCHiGVgDwm-B=xx8coDQKKFXUwuq8qzuTOxhaA8Q@mail.gmail.com>

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

      reply	other threads:[~2011-07-14  7:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

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=CA445423.1DD69%keir.xen@gmail.com \
    --to=keir.xen@gmail.com \
    --cc=maillists.shan@gmail.com \
    --cc=xen-devel@lists.xensource.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.