[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1181485863.384.15.camel@chaos>
Date: Sun, 10 Jun 2007 16:31:03 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Andreas Mohr <andi@...x01.hs-esslingen.de>
Cc: LKML <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...l.org>,
Ingo Molnar <mingo@...e.hu>, Andi Kleen <ak@...e.de>,
Arjan van de Ven <arjan@...radead.org>,
Venkatesh Pallipadi <venkatesh.pallipadi@...el.com>,
Chris Wright <chrisw@...s-sol.org>,
john stultz <johnstul@...ibm.com>
Subject: Re: [patch-mm 07/23] Tick management: spread timer interrupt
On Sun, 2007-06-10 at 16:16 +0200, Andreas Mohr wrote:
> Hi,
>
> On Sun, Jun 10, 2007 at 09:44:05AM -0000, Thomas Gleixner wrote:
> > From: john stultz <johnstul@...ibm.com>
> >
> > After discussing w/ Thomas over IRC, it seems the issue is the sched
> > tick fires on every cpu at the same time, causing extra lock contention.
>
> Hmm, the cpu-specific offset calculation isn't too expensive, hopefully?
> (div/mul in patch, maybe this could be done differently)
That's one time during setup, no hot path.
tglx
-
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