virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: nitesh narayan lal <niteshnarayanlalleo@gmail.com>
Cc: virtualization@lists.linux-foundation.org
Subject: Re: virtio performance analysis
Date: Tue, 14 May 2013 10:53:17 +0300	[thread overview]
Message-ID: <20130514075317.GC4368@redhat.com> (raw)
In-Reply-To: <CAAtA1-bmzJdmnCBifU+peaxiYTkG9S-Z9CsRdZkFQkHxL=4WGw@mail.gmail.com>

On Tue, May 14, 2013 at 11:37:35AM +0530, nitesh narayan lal wrote:
> I was wondering how exactly vq->event is been set and used?
> Regards
> Nitesh Narayan Lal
> 
> 
> On Tue, May 14, 2013 at 11:37 AM, nitesh narayan lal
> <niteshnarayanlalleo@gmail.com> wrote:
> > Hi Michael,
> > I had seen the virtqueue_kick_prepare() where vring_need_event() is
> > been used, but somehow for every start_xmit() call vq->event and
> > need_kick is been set to true.
> > Due to which for every start_xmit() its kicking via notify() routine.
> > Regards
> > Nitesh Narayan Lal


vq->event if set when guest and host agree to use event index.
needs_kick comes from comparison of event index (element for
which host requested an event) and avail index.

We trigger the event when we make available the element
for which host requested notification.

More detail in the virtio spec.

-- 
MST

  reply	other threads:[~2013-05-14  7:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-02  3:43 virtio performance analysis nitesh narayan lal
2013-05-06 10:19 ` Michael S. Tsirkin
     [not found]   ` <CAAtA1-ZTU7oance7f4=eHGqAf-g+u5e+JwPHMp3iAusHgBphLQ@mail.gmail.com>
2013-05-14  6:07     ` nitesh narayan lal
2013-05-14  6:07       ` nitesh narayan lal
2013-05-14  7:53         ` Michael S. Tsirkin [this message]
2013-05-14 12:34           ` nitesh narayan lal
  -- strict thread matches above, loose matches on Subject: below --
2013-05-01  6:49 nitesh narayan lal
2013-04-30 11:36 virtio Performance Analysis nitesh narayan lal

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=20130514075317.GC4368@redhat.com \
    --to=mst@redhat.com \
    --cc=niteshnarayanlalleo@gmail.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).