From: Darren Hart <darren@dvhart.com>
To: "Christopher Friesen" <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: help? converting to single global prio_array in scheduler, ran into snag
Date: Wed, 5 Apr 2006 20:34:02 -0700 [thread overview]
Message-ID: <200604052034.02962.darren@dvhart.com> (raw)
In-Reply-To: <4433FCF5.7080604@nortel.com>
On Wednesday 05 April 2006 10:23, you wrote:
> I should clarify that CKRM is currently disabled--I'm trying to get the
> vanilla scheduler working first before changing the CKRM stuff to use
> per-class prio arrays rather than per-class per-cpu ones.
>
First thing that comes to mind, did you look for every place that accesses the
arrays via the rq->lock and make it use the new global array_lock? It would
help if you would post your initial patch for review (designating it as RFC,
not intended for inclusion).
(Chris, sorry for the duplicate, forgot to cc the list first time around)
Thanks,
--Darren
next prev parent reply other threads:[~2006-04-06 3:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-05 16:54 help? converting to single global prio_array in scheduler, ran into snag Christopher Friesen
2006-04-05 17:23 ` Christopher Friesen
2006-04-06 3:34 ` Darren Hart [this message]
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=200604052034.02962.darren@dvhart.com \
--to=darren@dvhart.com \
--cc=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