All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: nitesh narayan lal <niteshnarayanlalleo@gmail.com>, agraf@suse.de
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: virtio performance analysis
Date: Mon, 6 May 2013 13:19:36 +0300	[thread overview]
Message-ID: <20130506101936.GA16906@redhat.com> (raw)
In-Reply-To: <CAAtA1-aB_EQruG8ta=xjt8LO-522_5=YbKCL_33exXG2n5vutw@mail.gmail.com>

On Thu, May 02, 2013 at 09:13:29AM +0530, nitesh narayan lal wrote:
> Hi,
> I am currently working on the virtio performance analysis in PowerPC .

That's nice.

> I was looking at the virtio front-end code and had done tracing by
> adding WARN_ON condition in skb_recv_done(),xmit_skb_done(
> ) and virtqueue_kick().

That's a bit heavy-handed. Why not just use ftrace?

> What I had seen is virtqueue_kick() internally it calls iowrite16()
> which will cause an exit to QEMU,

You probably should be looking at vhost-net and not
userspace virtio-net if you are interested in performance.

> now either I send a packets from
> Guest or receive a packets to guest sart_xmit() will be called and
> inside start_xmit there is a call to virtqueue_kick() causing Guest
> exit. Also for every packet or ack sent from Guest there is an
> exception received while sending or receiving the next packet/ack.

Not exactly, we can buffer many events in
case guest and host are running in parallel.
See vring_need_event and its uses.

> Due to all of the above factors mentioned their will be an increase in
> signal, EXTINT and guest exits

Increase as compared to what?

>  and hence it will effect the CPU
> performance.
> This is what my analysis is so far, it would be great if I could get
> some help on this such that whether it seems appropriate or not ?
> Regards
> Nitesh Narayan Lal
> _______________________________________________
> Virtualization mailing list
> Virtualization@lists.linux-foundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2013-05-06 10:19 UTC|newest]

Thread overview: 10+ 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 [this message]
     [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
2013-05-14 12:34           ` nitesh narayan lal
  -- strict thread matches above, loose matches on Subject: below --
2013-05-02  8:22 nitesh narayan lal
2013-05-01  6:49 nitesh narayan lal
2013-05-01  6:22 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=20130506101936.GA16906@redhat.com \
    --to=mst@redhat.com \
    --cc=agraf@suse.de \
    --cc=kvm@vger.kernel.org \
    --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 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.