public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Christopher Friesen" <cfriesen@nortel.com>
To: linux-kernel@vger.kernel.org
Subject: help? converting to single global prio_array in scheduler, ran into snag
Date: Wed, 05 Apr 2006 10:54:14 -0600	[thread overview]
Message-ID: <4433F636.3090705@nortel.com> (raw)


We're having some issues with the load balancer algorithm in CKRM, so 
due to time pressure I'm looking at converting the scheduler to use a 
single global prio_array rather than the per-cpu ones that it currently 
uses.  I realize we're going to take a hit, but we don't have too many 
cpus so I'm hoping it won't be too bad.

So far I've removed arrays/expired/active from the runqueue and made 
them global, added a new spinlock to protect the global list (always 
taken after the runqueue lock), and converted all the callers to use the 
appropriate variable.  All changes were in sched.h and sched.c.

This builds for both UP and SMP, boots for UP, and boots for SMP if I 
set the "nosmp" boot arg.

Unfortunately I seem to have missed something. On my Mac G5 if I allow 
it to use both cpus it gets to "smp_core99_setup_cpu 0 done", then hangs.

Anyone have any suggestions as to what I should look at?  Maybe the idle 
task initialization?

Thanks,

Chris


             reply	other threads:[~2006-04-05 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-05 16:54 Christopher Friesen [this message]
2006-04-05 17:23 ` help? converting to single global prio_array in scheduler, ran into snag Christopher Friesen
2006-04-06  3:34   ` Darren Hart
2006-04-06 16:08     ` Christopher Friesen

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=4433F636.3090705@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    /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