public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suresh Siddha <suresh.b.siddha@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Dave Jones <davej@redhat.com>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: sched domains oddness.
Date: Fri, 31 Oct 2008 10:09:29 -0700	[thread overview]
Message-ID: <20081031170928.GB10468@linux-os.sc.intel.com> (raw)
In-Reply-To: <1225471911.7803.1596.camel@twins>

On Fri, Oct 31, 2008 at 09:51:51AM -0700, Peter Zijlstra wrote:
> On Fri, 2008-10-31 at 12:24 -0400, Dave Jones wrote:
> > The attached dmesg comes from my dual core laptop running 2.6.27
> > What's up with all the sched domains transitions at the bottom?
> > This was just a boot up from power off, no suspend/resume or anything funky.
> 
> > CPU0 attaching NULL sched-domain.
> > CPU1 attaching NULL sched-domain.
> > CPU0 attaching sched-domain:
> >  domain 0: span 0-1 level MC
> >   groups: 0 1
> >   domain 1: span 0-1 level NODE
> >    groups: 0-1
> > CPU1 attaching sched-domain:
> >  domain 0: span 0-1 level MC
> >   groups: 1 0
> >   domain 1: span 0-1 level NODE
> >    groups: 0-1
> 
> 3x
> 
> looks like someone is triggering rebuild_sched_domains(), is something
> poking cpusetfs files or flipping between sched_mc settings?

I remember someone mentioning that some distro's started setting
sched_mc_power_savings to '1' by default during boot. On a dual-core
laptop, this will not give any advantage.

I have to fix the code to not export this tunable, when we have only
socket in the system.

Dave, Is your distro also setting this tunable blindly during boot :(

thanks,
suresh

  reply	other threads:[~2008-10-31 17:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-31 16:24 sched domains oddness Dave Jones
2008-10-31 16:51 ` Peter Zijlstra
2008-10-31 17:09   ` Suresh Siddha [this message]
2008-10-31 17:17     ` Dave Jones
2008-10-31 17:37       ` Dave Jones
2008-10-31 17:58         ` Suresh Siddha
2008-10-31 19:08     ` Dave Jones
2008-10-31 17:19   ` Dave Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081031170928.GB10468@linux-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox