DPDK patches and discussions
 help / color / mirror / Atom feed
From: Luke Gorrie <luke@snabb.co>
To: "snabb-devel@googlegroups.com" <snabb-devel@googlegroups.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	VirtualOpenSystems Technical Team <tech@virtualopensystems.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [dpdk-dev] [snabb-devel] Re: memory barriers in virtq.lua?
Date: Wed, 8 Apr 2015 05:40:11 +0200	[thread overview]
Message-ID: <CAA2XHbehi0rFuEGXDA=KTeVr5My1gvUOpOjFP5oSEUiYozrdCA@mail.gmail.com> (raw)
In-Reply-To: <20150407172849-mutt-send-email-mst@redhat.com>

On 7 April 2015 at 17:30, Michael S. Tsirkin <mst@redhat.com> wrote:

> Just guessing from the available info:
>
> I think you refer to this:
>         The driver MUST handle spurious interrupts from the device.
>
> The intent is to be able to handle some spurious interrupts once in a
> while.  AFAIK linux triggers the message if it gets a huge number of
> spurious interrupts for an extended period of time.
> For example, this will trigger if the device does not clear interrupt
> line after interrupt register read.
>

Thanks for that info.

The only spurious interrupt that I think we need is one when vhost-user
reconnects. That would be to cover the case where the vswitch is restarted
after writing used->idx but before sending the interrupt.

Or perhaps there is a better solution to that case?

Looking forward to getting an upstream vhost-user reconnect. one thing at a
time.. :)

Cheers,
-Luke

  reply	other threads:[~2015-04-08  3:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150127160126.GA10651@redhat.com>
     [not found] ` <CADDJ2=M6hwFwooXqUjUc9+JxjW1sVYvKhY9dBavrmMUrej6Ysw@mail.gmail.com>
2015-04-07 14:22   ` Luke Gorrie
2015-04-07 15:30     ` Michael S. Tsirkin
2015-04-08  3:40       ` Luke Gorrie [this message]
2015-04-08 15:15     ` Xie, Huawei
2015-04-09  3:12       ` Luke Gorrie
2015-04-09 15:00         ` Xie, Huawei

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='CAA2XHbehi0rFuEGXDA=KTeVr5My1gvUOpOjFP5oSEUiYozrdCA@mail.gmail.com' \
    --to=luke@snabb.co \
    --cc=dev@dpdk.org \
    --cc=snabb-devel@googlegroups.com \
    --cc=tech@virtualopensystems.com \
    --cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).