From: Sasha Levin <levinsasha928@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: penberg@kernel.org, kvm@vger.kernel.org, asias.hejun@gmail.com,
gorcunov@gmail.com, prasadjoshi124@gmail.com
Subject: Re: [PATCH] kvm tools: Add MMIO coalescing support
Date: Sat, 04 Jun 2011 13:14:01 +0300 [thread overview]
Message-ID: <1307182441.7239.2.camel@lappy> (raw)
In-Reply-To: <20110604093847.GB14524@elte.hu>
On Sat, 2011-06-04 at 11:38 +0200, Ingo Molnar wrote:
> * Sasha Levin <levinsasha928@gmail.com> wrote:
>
> > Coalescing MMIO allows us to avoid an exit every time we have a
> > MMIO write, instead - MMIO writes are coalesced in a ring which
> > can be flushed once an exit for a different reason is needed.
> > A MMIO exit is also trigged once the ring is full.
> >
> > Coalesce all MMIO regions registered in the MMIO mapper.
> > Add a coalescing handler under kvm_cpu.
>
> Does this have any effect on latency? I.e. does the guest side
> guarantee that the pending queue will be flushed after a group of
> updates have been done?
Theres nothing that detects groups of MMIO writes, but the ring size is
a bit less than PAGE_SIZE (half of it is overhead - rest is data) and
we'll exit once the ring is full.
--
Sasha.
next prev parent reply other threads:[~2011-06-04 10:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 19:51 [PATCH] kvm tools: Add MMIO coalescing support Sasha Levin
2011-06-04 9:38 ` Ingo Molnar
2011-06-04 10:14 ` Sasha Levin [this message]
2011-06-04 10:17 ` Ingo Molnar
2011-06-04 10:28 ` Sasha Levin
2011-06-04 10:35 ` Ingo Molnar
2011-06-04 10:39 ` Alexander Graf
2011-06-04 10:47 ` Ingo Molnar
2011-06-04 10:54 ` Alexander Graf
2011-06-04 11:27 ` Ingo Molnar
2011-06-04 11:53 ` Alexander Graf
2011-06-04 14:46 ` Ingo Molnar
2011-06-04 15:22 ` Alexander Graf
2011-06-04 16:34 ` Ingo Molnar
2011-06-04 16:50 ` Sasha Levin
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=1307182441.7239.2.camel@lappy \
--to=levinsasha928@gmail.com \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=prasadjoshi124@gmail.com \
/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