From: Jim Houston <jim.houston@attbi.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] O(1) CPU time accounting
Date: Tue, 05 Nov 2002 16:26:54 -0500 [thread overview]
Message-ID: <3DC8379E.20F9EA33@attbi.com> (raw)
In-Reply-To: Pine.LNX.4.44L.0211051523280.3411-100000@imladris.surriel.com
Rik van Riel wrote:
>
> Hi Jim,
>
> this incremental patch (over your O(1) CPU time patch) makes
> nice levels work again, though they are fairly steep now:
>
> This might be a decent basis for an O(1) per-user fair
> scheduler, after some more balancing and cleaning up of
> excess code.
Hi Rik,
Your changes look reasonable. I will give them a try.
I'm hoping to get back to playing with scheduler fairness
patchs soon. I made the mistake of starting a re-write of
Posix timers so it may be a few more days.
If anyone else is trying to follow this my patch is
archive here:
http://marc.theaimsgroup.com/?l=linux-kernel&m=103508412423719&w=2
Jim Houston - Concurrent Computer Corp.
prev parent reply other threads:[~2002-11-05 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 17:24 [PATCH] O(1) CPU time accounting Rik van Riel
2002-11-05 21:26 ` Jim Houston [this message]
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=3DC8379E.20F9EA33@attbi.com \
--to=jim.houston@attbi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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