From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Nick's scheduler policy v7
Date: Mon, 25 Aug 2003 16:36:12 +0200 [thread overview]
Message-ID: <yw1xd6etrehv.fsf@users.sourceforge.net> (raw)
In-Reply-To: 3F49E7D1.4000309@cyberone.com.au
Nick Piggin <piggin@cyberone.com.au> writes:
> This one has a few changes. Children now get a priority boost
> on fork, and parents retain more priority after forking a child,
> however exiting CPU hogs will now penalise parents a bit.
>
> Timeslice scaling was tweaked a bit. Oh and remember raising X's
> priority should _help_ interactivity with this patch, and IMO is
> not an unreasonable thing to be doing.
>
> Please test. I'm not getting enough feedback!
OK, if you test my software.
Seriously, though, it seems OK at first glance. I can't reproduce the
XEmacs problems I had with Con's recent versions. I'll have to run it
for a while and see what it seems like.
--
Måns Rullgård
mru@users.sf.net
next prev parent reply other threads:[~2003-08-25 14:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-24 12:35 [PATCH] Nick's scheduler policy Nick Piggin
2003-08-24 14:29 ` Felipe Alfaro Solana
2003-08-25 3:05 ` Nick Piggin
2003-08-25 22:30 ` Bill Davidsen
2003-08-24 16:55 ` Martin J. Bligh
2003-08-25 3:00 ` Nick Piggin
2003-08-25 10:41 ` [PATCH] Nick's scheduler policy v7 Nick Piggin
2003-08-25 11:03 ` Felipe Alfaro Solana
2003-08-25 14:36 ` Måns Rullgård [this message]
2003-08-26 3:24 ` Martin J. Bligh
2003-08-26 4:04 ` Nick Piggin
2003-08-26 9:44 ` Yaroslav Rastrigin
2003-08-27 9:28 ` Mike Galbraith
2003-08-25 3:27 ` [PATCH] Nick's scheduler policy Randy.Dunlap
2003-08-25 3:36 ` Nick Piggin
2003-08-26 3:16 ` Mike Fedyk
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=yw1xd6etrehv.fsf@users.sourceforge.net \
--to=mru@users.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.