From: Jeremy Fitzhardinge Subject: Re: lmbench lat_mmap slowdown with CONFIG_PARAVIRT Date: Wed, 21 Jan 2009 14:23:13 -0800 Message-ID: <4977A051.8050203@goop.org> References: <20090120110542.GE19505@wotan.suse.de> <20090120112634.GA20858@elte.hu> <20090120140324.GA26424@elte.hu> <49763806.5090009@goop.org> <20090120205653.GA19710@elte.hu> <20090121072718.GN24891@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090121072718.GN24891@wotan.suse.de> Sender: linux-kernel-owner@vger.kernel.org To: Nick Piggin Cc: Ingo Molnar , 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 Nick Piggin wrote: > 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? > I assume so. There should be no extra data accesses with CONFIG_PARAVIRT (hm, there's probably some extra stack/spill traffic, but I surely hope that's not falling out of cache). J