From: Linhaifeng <haifeng.lin@huawei.com>
To: <netdev@vger.kernel.org>
Cc: <virtualization@lists.linux-foundation.org>,
"rusty@rustcorp.com.au >> Rusty Russell" <rusty@rustcorp.com.au>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: virtio-net: why not always to set avail->flags to VRING_AVAIL_F_NO_INTERRUPT
Date: Wed, 3 Jun 2015 14:32:39 +0800 [thread overview]
Message-ID: <556E9F87.7030202@huawei.com> (raw)
Hi,
I'm a newbie and have a question about vring_new_virtqueue function.
Why we set avail->flags to VRING_AVAIL_F_NO_INTERRUPT when no callbacks?
I think we should set avail->flags to VRING_AVAIL_F_NO_INTERRUPT even if no callbacks.
next reply other threads:[~2015-06-03 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 6:32 Linhaifeng [this message]
2015-06-04 1:13 ` virtio-net: why not always to set avail->flags to VRING_AVAIL_F_NO_INTERRUPT Rusty Russell
2015-06-04 1:13 ` Rusty Russell
2015-06-04 2:35 ` Linhaifeng
2015-06-04 2:35 ` Linhaifeng
2015-06-04 19:52 ` Rusty Russell
-- strict thread matches above, loose matches on Subject: below --
2015-06-03 6:32 Linhaifeng
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=556E9F87.7030202@huawei.com \
--to=haifeng.lin@huawei.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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 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.