From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Alexander Graf <agraf@suse.de>,
Marcelo Tosatti <mtosatti@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
Takuya Yoshikawa <yoshikawa_takuya_b1@lab.ntt.co.jp>,
Alex Williamson <alex.williamson@redhat.com>,
Will Deacon <will.deacon@arm.com>,
Christoffer Dall <c.dall@virtualopensystems.com>,
Sasha Levin <sasha.levin@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH RFC] kvm: add PV MMIO EVENTFD
Date: Sun, 7 Apr 2013 11:43:01 +0300 [thread overview]
Message-ID: <20130407084301.GC10317@redhat.com> (raw)
In-Reply-To: <20130407093038.GL17919@redhat.com>
On Sun, Apr 07, 2013 at 12:30:38PM +0300, Gleb Natapov wrote:
> On Thu, Apr 04, 2013 at 04:14:57PM +0300, Gleb Natapov wrote:
> > > >
> > > >>> is to move to MMIO only when PIO address space is exhausted. For PCI it
> > > >>> will be never, for PCI-e it will be after ~16 devices.
> > > >>
> > > >> Ok, let's go back a step here. Are you actually able to measure any speed in performance with this patch applied and without when going through MMIO kicks?
> > > >>
> > > >>
> > > > That's the question for MST. I think he did only micro benchmarks till
> > > > now and he already posted his result here:
> > > >
> > > > mmio-wildcard-eventfd:pci-mem 3529
> > > > mmio-pv-eventfd:pci-mem 1878
> > > > portio-wildcard-eventfd:pci-io 1846
> > > >
> > > > So the patch speedup mmio by almost 100% and it is almost the same as PIO.
> > >
> > > Those numbers don't align at all with what I measured.
> > I am trying to run vmexit test on AMD now, but something does not work
> > there. Next week I'll fix it and see how AMD differs, bit on Intel those are the
> > numbers.
> >
> The numbers are:
> vmcall 1921
> inl_from_kernel 4227
> outl_to_kernel 2345
>
> outl is specifically optimized to not go through the emulator since it
> is used for virtio kick. mmio-pv-eventfd is the same kind of
> optimization but for mmio.
>
> --
> Gleb.
Hmm so on AMD it's more like 20% overhead, like ARM.
--
MST
next prev parent reply other threads:[~2013-04-07 9:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 10:50 Michael S. Tsirkin
2013-04-04 11:57 ` Alexander Graf
2013-04-04 11:04 ` Michael S. Tsirkin
2013-04-04 12:09 ` Alexander Graf
2013-04-04 11:21 ` Michael S. Tsirkin
2013-04-04 12:19 ` Gleb Natapov
2013-04-04 12:22 ` Alexander Graf
2013-04-04 12:08 ` Gleb Natapov
2013-04-04 12:22 ` Alexander Graf
2013-04-04 12:34 ` Gleb Natapov
2013-04-04 12:39 ` Alexander Graf
2013-04-04 12:58 ` Michael S. Tsirkin
2013-04-04 14:02 ` Alexander Graf
2013-04-04 13:40 ` Michael S. Tsirkin
2013-04-04 12:32 ` Alexander Graf
2013-04-04 12:38 ` Gleb Natapov
2013-04-04 12:39 ` Alexander Graf
2013-04-04 12:45 ` Gleb Natapov
2013-04-04 12:49 ` Alexander Graf
2013-04-04 12:56 ` Gleb Natapov
2013-04-04 13:06 ` Alexander Graf
2013-04-04 13:14 ` Gleb Natapov
2013-04-04 14:26 ` Michael S. Tsirkin
2013-04-07 9:30 ` Gleb Natapov
2013-04-07 8:43 ` Michael S. Tsirkin [this message]
2013-04-04 13:33 ` Michael S. Tsirkin
2013-04-04 15:36 ` Alexander Graf
2013-04-04 15:36 ` Michael S. Tsirkin
2013-04-04 16:39 ` Gleb Natapov
2013-04-04 23:32 ` Christoffer Dall
2013-04-07 7:41 ` Michael S. Tsirkin
2013-04-07 21:25 ` Christoffer Dall
2013-04-04 16:33 ` Gleb Natapov
2013-04-04 13:12 ` Michael S. Tsirkin
2013-04-04 13:06 ` Michael S. Tsirkin
2013-04-04 13:03 ` Michael S. Tsirkin
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=20130407084301.GC10317@redhat.com \
--to=mst@redhat.com \
--cc=agraf@suse.de \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=c.dall@virtualopensystems.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=sasha.levin@oracle.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=will.deacon@arm.com \
--cc=x86@kernel.org \
--cc=xiaoguangrong@linux.vnet.ibm.com \
--cc=yoshikawa_takuya_b1@lab.ntt.co.jp \
/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
Powered by JetHome