From: Robert Love <rml@tech9.net>
To: Antonio Vargas <wind@cocodriloo.com>
Cc: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: fairsched + O(1) process scheduler
Date: 02 Apr 2003 16:35:00 -0500 [thread overview]
Message-ID: <1049319300.2872.21.camel@localhost> (raw)
In-Reply-To: <20030402213629.GB13168@wind.cocodriloo.com>
On Wed, 2003-04-02 at 16:36, Antonio Vargas wrote:
> I've been thinking about this thing a while ago, and I think I could do this:
>
> a. Have a kernel thread which wakes up on each tick.
Why not use the timer tick itself? It already calls scheduler_tick()...
Oh, because you need to grab uidhash_lock? Ew. Needing a kernel thread
for this is not pretty.
> Also, this locking rule means I can't even read current->user->time_slice?
> What if I changed the type to an atomic_int?
You can always read a single word-sized type atomically. No need for
atomic_t's.
Robert Love
next prev parent reply other threads:[~2003-04-02 21:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 12:51 fairsched + O(1) process scheduler Antonio Vargas
2003-04-01 16:41 ` William Lee Irwin III
2003-04-01 22:19 ` Antonio Vargas
2003-04-02 12:46 ` Antonio Vargas
2003-04-02 16:35 ` William Lee Irwin III
2003-04-02 21:36 ` Antonio Vargas
2003-04-02 21:35 ` Robert Love [this message]
2003-04-02 22:07 ` Antonio Vargas
2003-04-02 22:10 ` Robert Love
2003-04-02 22:35 ` Antonio Vargas
2003-04-03 17:15 ` Corey Minyard
2003-04-03 18:17 ` Robert Love
[not found] ` <200304021144.21924.frankeh@watson.ibm.com>
2003-04-03 12:53 ` Antonio Vargas
2003-04-03 19:22 ` William Lee Irwin III
2003-04-04 11:27 ` Antonio Vargas
2003-04-04 14:04 ` William Lee Irwin III
2003-04-04 20:12 ` Antonio Vargas
2003-04-04 20:40 ` William Lee Irwin III
[not found] ` <200304041453.16630.frankeh@watson.ibm.com>
2003-04-04 21:36 ` Antonio Vargas
[not found] ` <200304081456.34367.frankeh@watson.ibm.com>
2003-04-08 20:19 ` Antonio Vargas
2003-04-01 18:33 ` Robert Love
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=1049319300.2872.21.camel@localhost \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=wind@cocodriloo.com \
--cc=wli@holomorphy.com \
/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