From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takuya Yoshikawa 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 Message-ID: <20120315224142.67713f557239116a99cd18af@gmail.com> References: <20120315181856.2ced0a28.yoshikawa.takuya@oss.ntt.co.jp> <20120315182127.07600c50.yoshikawa.takuya@oss.ntt.co.jp> <4F61BB1D.6050209@redhat.com> <20120315191553.32d6fc36.yoshikawa.takuya@oss.ntt.co.jp> <4F61DA07.4010200@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Takuya Yoshikawa , mtosatti@redhat.com, kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from mail-gx0-f174.google.com ([209.85.161.174]:48302 "EHLO mail-gx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753526Ab2CONls (ORCPT ); Thu, 15 Mar 2012 09:41:48 -0400 Received: by gghe5 with SMTP id e5so3043991ggh.19 for ; Thu, 15 Mar 2012 06:41:47 -0700 (PDT) In-Reply-To: <4F61DA07.4010200@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Avi Kivity 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