public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Chad N. Tindel" <chad@tindel.net>
To: linux-kernel@vger.kernel.org
Subject: Scheduler question in __wake_up_common() - Real Time Apps
Date: Mon, 28 Feb 2005 13:30:36 -0500	[thread overview]
Message-ID: <20050228183036.GA22914@calma.pair.com> (raw)

I have a question about the implementation in __wake_up_common() that I'm
hoping someone might know the background on.  This function wakes up
a specified number of tasks for a wait_queue.  I'm wondering why it doesn't
wake up the tasks in priority order, so that for things following wake-one 
semantics high priority tasks get woken up before lower priority tasks.

The only thing I can think of off the top of my head is that it simplifies the 
O(1) implementation, but I'm wondering if maybe there is something else.

Thanks,

Chad

             reply	other threads:[~2005-02-28 18:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-28 18:30 Chad N. Tindel [this message]
2005-02-28 20:44 ` Scheduler question in __wake_up_common() - Real Time Apps Steven Rostedt

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=20050228183036.GA22914@calma.pair.com \
    --to=chad@tindel.net \
    --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