From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: Xen spinlock questions Date: Wed, 06 Aug 2008 13:21:53 -0700 Message-ID: <489A07E1.6070808@goop.org> References: <4896F39A.76E4.0078.0@novell.com> <48975A30.2080408@goop.org> <48981005.76E4.0078.0@novell.com> <4898976A.3080406@goop.org> <48996BB8.76E4.0078.0@novell.com> <48996536.1030303@goop.org> <48998C7E.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <48998C7E.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich Cc: xen-devel@lists.xensource.com, Keir Fraser List-Id: xen-devel@lists.xenproject.org Jan Beulich wrote: >> In my tests, I only see it fall into the slow path a couple of thousand >> times per cpu for a kernbench run. >> > > Hmm, that's different then for me. Actually, I see a significant spike at > modpost stage 2, when all the .ko-s get linked. The (spinlock) interrupt > rate gets up to between 1,000 and 2,000 per CPU and second. > BTW, how much contention for CPUs was there? J