[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.00.0909090120531.25928@twin.jikos.cz>
Date: Wed, 9 Sep 2009 01:20:59 +0200 (CEST)
From: Jiri Kosina <jkosina@...e.cz>
To: Nikos Chantziaras <realnc@...or.de>
Cc: Juergen Beisert <jbe@...gutronix.de>, linux-kernel@...r.kernel.org,
Arjan van de Ven <arjan@...radead.org>
Subject: Re: BFS vs. mainline scheduler benchmarks and measurements
On Wed, 9 Sep 2009, Nikos Chantziaras wrote:
> > > Here the result:
> > >
> > > http://foss.math.aegean.gr/~realnc/pics/latop2.png
> > >
> > > Again: this is on an Intel Core 2 Duo CPU.
> >
> > Just an idea: Maybe some system management code hits you?
>
> I'm not sure what is meant with "system management code."
System management interrupt happens when firmware/BIOS/HW-debugger is
executed in privilege mode so high, that even OS can't do anything about
that.
It is used in many situations, such as
- memory errors
- ACPI (mostly fan control)
- TPM
OS has small to none possibility to influence SMI/SMM. But if this would
be the cause, you should probably obtain completely different results on
different hardware configuration (as it is likely to have completely
different SMM behavior).
--
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists