From: Nick Piggin Subject: Re: lmbench lat_mmap slowdown with CONFIG_PARAVIRT Date: Wed, 21 Jan 2009 08:27:18 +0100 Message-ID: <20090121072718.GN24891@wotan.suse.de> References: <20090120110542.GE19505@wotan.suse.de> <20090120112634.GA20858@elte.hu> <20090120140324.GA26424@elte.hu> <49763806.5090009@goop.org> <20090120205653.GA19710@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20090120205653.GA19710@elte.hu> Sender: linux-kernel-owner@vger.kernel.org To: Ingo Molnar Cc: Jeremy Fitzhardinge , Linux Kernel Mailing List , Linus Torvalds , hpa@zytor.com, jeremy@xensource.com, chrisw@sous-sol.org, zach@vmware.com, rusty@rustcorp.com.au, Andrew Morton , Xen-devel List-Id: xen-devel@lists.xenproject.org On Tue, Jan 20, 2009 at 09:56:53PM +0100, Ingo Molnar wrote: > > * Jeremy Fitzhardinge wrote: > >> | 50234816 | 51303520 cache references +2.12% > >> | 5428258 | 5583728 cache misses +2.86% > >> > > > > Is this I or D, or combined? > > That's last-level-cache references+misses (L2 cache): > > Bit Position Event Name UMask Event Select > CPUID.AH.EBX > 3 LLC Reference 4FH 2EH > 4 LLC Misses 41H 2EH Oh, _llc_ references/misses? Ouch. You have, what 32K L1I, 32K L1D, and 4MB L2? And even this microbenchmark is seeing increased L2 misses by nearly 3%. Hmm, I wonder where that is coming from? Instruction fetches? It would be interesting to see how "the oltp" benchmark fares with CONFIG_PARAVIRT turned on. That workload lives and dies by the cache :)