From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
Cc: Eric Northup <digitaleric@google.com>, KVM <kvm@vger.kernel.org>
Subject: Re: [RFC] KVM MMU: improve large munmap efficiency
Date: Sun, 29 Jan 2012 15:25:59 +0200 [thread overview]
Message-ID: <4F2548E7.9070807@redhat.com> (raw)
In-Reply-To: <20120129222250.c69609adad5dd196cda91575@gmail.com>
On 01/29/2012 03:22 PM, Takuya Yoshikawa wrote:
> On Sun, 29 Jan 2012 13:01:18 +0200
> Avi Kivity <avi@redhat.com> wrote:
>
> > > Tested by attaching a debugger to a running qemu w/kvm and running
> > > "call munmap(0, 1UL << 46)".
> > >
> >
> > How about computing the intersection of (start, end) with the hva ranges
> > in kvm->memslots?
> >
> > If there is no intersection, you exit immediately.
>
> I think introducing kvm_handle_hva_range() is the right thing if we really
> care about unmapping large area at once.
>
> Current iteration:
> for each page
> for each slot
> for each level
>
> My suggestion:
> for each slot
> for each level
> for each page
>
> This way compiler can optimize the task to be a simple iteration over the
> rmap array.
Yes. This automatically includes the intersection calculation, since
you have to do it for the 'for each page in slot' loop.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-01-29 13:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 23:24 [RFC] KVM MMU: improve large munmap efficiency Eric Northup
2012-01-27 0:59 ` Takuya Yoshikawa
2012-01-27 1:13 ` Takuya Yoshikawa
2012-01-29 11:01 ` Avi Kivity
2012-01-29 13:22 ` Takuya Yoshikawa
2012-01-29 13:25 ` Avi Kivity [this message]
2012-01-29 13:50 ` Takuya Yoshikawa
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=4F2548E7.9070807@redhat.com \
--to=avi@redhat.com \
--cc=digitaleric@google.com \
--cc=kvm@vger.kernel.org \
--cc=takuya.yoshikawa@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 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.