From: Peter Osterlund <petero2@telia.com>
To: Davide Libenzi <davidel@xmailserver.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: [PATCH] scheduler fixups ...
Date: 02 Jan 2002 23:31:04 +0100 [thread overview]
Message-ID: <m28zbgpeqf.fsf@pengo.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.40.0201021236390.1034-100000@blue1.dev.mcafeelabs.com>
In-Reply-To: <Pine.LNX.4.40.0201021236390.1034-100000@blue1.dev.mcafeelabs.com>
Davide Libenzi <davidel@xmailserver.org> writes:
> a still lower ts
This also lowers the effectiveness of nice values. In 2.5.2-pre6, if I
run two cpu hogs at nice values 0 and 19 respectively, the niced task
will get approximately 20% cpu time (on x86 with HZ=100) and this
patch will give even more cpu time to the niced task. Isn't 20% too
much?
--
Peter Osterlund - petero2@telia.com
http://w1.894.telia.com/~u89404340
next prev parent reply other threads:[~2002-01-02 22:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-02 20:41 Davide Libenzi
2002-01-02 22:31 ` Peter Osterlund [this message]
2002-01-02 22:48 ` Davide Libenzi
2002-01-03 0:36 ` Peter Osterlund
2002-01-03 0:55 ` Davide Libenzi
2002-01-03 12:54 ` Rik van Riel
2002-01-03 17:36 ` Davide Libenzi
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=m28zbgpeqf.fsf@pengo.localdomain \
--to=petero2@telia.com \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®