From: Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
To: Avi Kivity <avi@redhat.com>
Cc: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>,
mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH 3/3] KVM: MMU: Separate trivial NULL check out from rmap_get_next()
Date: Thu, 15 Mar 2012 22:41:42 +0900 [thread overview]
Message-ID: <20120315224142.67713f557239116a99cd18af@gmail.com> (raw)
In-Reply-To: <4F61DA07.4010200@redhat.com>
Avi Kivity <avi@redhat.com> wrote:
> > What I checked was:
> >
> > original with-patch2 with-patch3
> > 8.7ms 8.5ms 7.5ms
>
> What's the per-call numbers?
I did not look into details at that time.
I will try to see more details later if possible!
> What I mean is, modern cpus effectively inline simple function calls by
> predicting the call, and branchs within the function, and the return, so
> they don't have to stop their pipelines at any of these points. But
> again, the numbers talk louder than speculation about cpu architecture.
I need to update my knowledge, thank you!
Anyway I will re-check if we can achieve the same performance with a bit
cleaner implementation.
Takuya
next prev parent reply other threads:[~2012-03-15 13:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 9:18 [PATCH 0/3] KVM: MMU: Improve rmap handling Takuya Yoshikawa
2012-03-15 9:19 ` [PATCH 1/3] KVM: MMU: Make pte_list_desc fit cache lines well Takuya Yoshikawa
2012-03-15 9:22 ` Avi Kivity
2012-03-15 9:20 ` [PATCH 2/3] KVM: MMU: Improve iteration over sptes linked by rmap Takuya Yoshikawa
2012-03-15 9:44 ` Avi Kivity
2012-03-15 10:25 ` Takuya Yoshikawa
2012-03-15 9:21 ` [PATCH 3/3] KVM: MMU: Separate trivial NULL check out from rmap_get_next() Takuya Yoshikawa
2012-03-15 9:49 ` Avi Kivity
2012-03-15 10:15 ` Takuya Yoshikawa
2012-03-15 12:01 ` Avi Kivity
2012-03-15 13:41 ` Takuya Yoshikawa [this message]
2012-03-15 13:45 ` Avi Kivity
2012-03-15 13:46 ` Avi Kivity
2012-03-20 6:37 ` Takuya Yoshikawa
2012-03-20 11:56 ` Avi Kivity
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=20120315224142.67713f557239116a99cd18af@gmail.com \
--to=takuya.yoshikawa@gmail.com \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=yoshikawa.takuya@oss.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 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.