From: Pozsar Balazs <pozsy@sch.bme.hu>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [test-PATCH] Re: [QUESTION] 2.4.x nice level
Date: Fri, 13 Apr 2001 00:51:30 +0200 [thread overview]
Message-ID: <20010413005130.A4438@balu.sch.bme.hu> (raw)
In-Reply-To: <Pine.LNX.4.21.0104110726210.25737-100000@imladris.rielhome.conectiva> <Pine.LNX.4.21.0104111251040.25737-100000@imladris.rielhome.conectiva>
In-Reply-To: <Pine.LNX.4.21.0104111251040.25737-100000@imladris.rielhome.conectiva>; from riel@conectiva.com.br on Wed, Apr 11, 2001 at 12:53:16PM -0300
On Wed, Apr 11, 2001 at 12:53:16PM -0300, Rik van Riel wrote:
> On Wed, 11 Apr 2001, Rik van Riel wrote:
>
> > OK, here it is. It's nothing like montavista's singing-dancing
> > scheduler patch that does all, just a really minimal change that
> > should stretch the nice levels to yield the following CPU usage:
> >
> > Nice 0 5 10 15 19
> > %CPU 100 56 25 6 1
>
> PID USER PRI NI SIZE SWAP RSS SHARE STAT %CPU %MEM TIME COMMAND
> 980 riel 17 0 296 0 296 240 R 54.1 0.5 54:19 loop
> 1005 riel 16 5 296 0 296 240 R N 27.0 0.5 0:34 loop
> 1006 riel 17 10 296 0 296 240 R N 13.5 0.5 0:16 loop
> 1007 riel 18 15 296 0 296 240 R N 4.5 0.5 0:05 loop
> 987 riel 20 19 296 0 296 240 R N 0.4 0.5 0:25 loop
How does this scale to negative nice levels? Afaik it should, in some way.
(I don't mean that it's wrong in this state, i'm just asking).
regards,
Balazs.
next prev parent reply other threads:[~2001-04-12 22:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 16:12 [QUESTION] 2.4.x nice level SodaPop
2001-04-10 3:37 ` george anzinger
2001-04-10 16:10 ` Rik van Riel
2001-04-10 16:39 ` george anzinger
2001-04-11 10:34 ` [test-PATCH] " Rik van Riel
2001-04-11 15:53 ` Rik van Riel
2001-04-12 22:51 ` Pozsar Balazs [this message]
2001-04-11 16:27 ` george anzinger
2001-04-12 23:51 ` Pavel Machek
2001-04-16 14:18 ` Rik van Riel
2001-04-16 17:49 ` george anzinger
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=20010413005130.A4438@balu.sch.bme.hu \
--to=pozsy@sch.bme.hu \
--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