public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Marc-Christian Petersen <m.c.p@wolk-project.de>
Cc: linux-kernel@vger.kernel.org, Kurt Garloff <garloff@suse.de>
Subject: Re: 2.4.22aa1
Date: Tue, 2 Sep 2003 20:54:53 +0200	[thread overview]
Message-ID: <20030902185453.GL1599@dualathlon.random> (raw)
In-Reply-To: <200309022037.39364.m.c.p@wolk-project.de>

On Tue, Sep 02, 2003 at 08:38:39PM +0200, Marc-Christian Petersen wrote:
> On Tuesday 02 September 2003 04:02, Andrea Arcangeli wrote:
> 
> Hi Andrea,
> 
> > Only in 2.4.22aa1: 20_sched-o1-fixes-10
> > Only in 2.4.22pre7aa1: 20_sched-o1-fixes-9
> > 	Changed the CHILD_PENALTY logic to be centered around
> > 	50%. From Kurt Garloff.
> 
> the changes 's/CHILD_PENALTY/CHILD_INHERITANCE' and "s/PARENT_PENALTIY//' are 
> really awfull for desktops. If I change child_inheritance from 60 to 95 and 
> reintroduce the logic with parent_penaltiy, it's alot smooter under load.
> 
> I think these logics should be #ifdef'ed with CONFIG_DESKTOP, no?

s/PARENT_PENALTIY// is a noop. The CHILD_INHERITANCE moves it from 50%
to 60% and center it in the middle. If something it will increase the
sleep_avg of the child that will lead to making the childs more
responsive. It sounds quite strange that backing out this, makes the
system more responsive. btw, Kurt developed this stuff with the object
of making it more responsive, not less. What could go wrong is that the
child will get more responsiveness than the parent and maybe for your
load the interactive app is the parent and not the child, dunno.

Andrea

/*
 * If you refuse to depend on closed software for a critical
 * part of your business, these links may be useful:
 *
 * rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.5/
 * rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.4/
 * http://www.cobite.com/cvsps/
 *
 * svn://svn.kernel.org/linux-2.6/trunk
 * svn://svn.kernel.org/linux-2.4/trunk
 */

  reply	other threads:[~2003-09-02 18:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-02  2:02 2.4.22aa1 Andrea Arcangeli
2003-09-02 10:59 ` 2.4.22aa1: scsi/pcmcia build failures Eyal Lebedinsky
2003-09-02 11:55 ` 2.4.22aa1 - unresolved Eyal Lebedinsky
2003-09-02 15:07   ` Andrea Arcangeli
2003-09-02 18:38 ` 2.4.22aa1 Marc-Christian Petersen
2003-09-02 18:54   ` Andrea Arcangeli [this message]
2003-09-02 21:07   ` 2.4.22aa1 Kurt Garloff

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=20030902185453.GL1599@dualathlon.random \
    --to=andrea@suse.de \
    --cc=garloff@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.c.p@wolk-project.de \
    /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