Date: Mon, 10 Nov 2008 09:58:46 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Alexander van Heukelum <heukelum@fastmail.fm>
Cc: Andi Kleen <andi@firstfloor.org>, Cyrill Gorcunov <gorcunov@gmail.com>,
       Alexander van Heukelum <heukelum@mailshack.com>,
       LKML <linux-kernel@vger.kernel.org>,
       Thomas Gleixner <tglx@linutronix.de>, "H. Peter Anvin" <hpa@zytor.com>,
       lguest@ozlabs.org, jeremy@xensource.com,
       Steven Rostedt <srostedt@redhat.com>, Mike Travis <travis@sgi.com>
Subject: Re: [PATCH RFC/RFB] x86_64, i386: interrupt dispatch changes
Message-ID: <20081110085846.GG22392@elte.hu>
References: <20081104122839.GA22864@mailshack.com> <20081104150729.GC21470@localhost> <20081104170501.GE29626@one.firstfloor.org> <1225822006.21441.1282961299@webmail.messagingengine.com> <20081104204400.GC10825@elte.hu> <1226243805.27361.1283784629@webmail.messagingengine.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1226243805.27361.1283784629@webmail.messagingengine.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1677
Lines: 37


* Alexander van Heukelum <heukelum@fastmail.fm> wrote:

> Hi all,
> 
> I have spent some time trying to find out how expensive the 
> segment-switching patch was. I have only one computer available at 
> the time: a "Sempron 2400+", 32-bit-only machine.
> 
> Measured were timings of "hackbench 10" in a loop. The average was 
> taken of more than 100 runs. Timings were done for two seperate 
> boots of the system.

hackbench is _way_ too noisy to measure such cycle-level differences 
as irq entry changes cause. It also does not really stress interrupts 
- it only stresses networking, the VFS and the scheduler.

a better test might have been to generate a ton of interrupts, but 
even then it's _very_ hard to measure it properly. The best method is 
what i've suggested to you early on: run a loop in user-space and 
observe irq costs via RDTSC, as they happen. Then build a histogram 
and compare the before/after histogram. Compare best-case results as 
well (the first slot of the histogram), as those are statistically 
much more significant than a noisy average.

Measuring such things in a meaningful way is really tricky business. 
Using hackbench to measure IRQ entry micro-costs is like trying to 
take a photo of a delicate flower at night, by using an atomic bomb as 
the flash-light: you certainly get some sort of effect to report, but 
there's not many nuances left in the picture to really look at ;-)

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/