mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Daniel Walker <dwalker@mvista.com>,
	linux-kernel@vger.kernel.org, peterz@infradead.org
Subject: Re: [ANNOUNCE/RFC] Really Fair Scheduler
Date: Sun, 2 Sep 2007 19:16:34 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709021903240.1817@scrub.home> (raw)
In-Reply-To: <20070902152900.GA23642@elte.hu>

Hi,

On Sun, 2 Sep 2007, Ingo Molnar wrote:

> so i thought you must be aware of the problem - at least considering how 
> much you've criticised CFS's "complexity" both in your initial review of 
> CFS (which included object size comparisons) and in this patch 
> submission of yours (which did not include object size comparisons
> though).

Ingo as long as you freely mix algorithmic and code complexity we won't 
get very far. I did code size comparisons for your _stable_ code, which 
was merged into Linus' tree. I explicitly said that my patch is only a 
prototype, so I haven't done any cleanups and tuning in this direction 
yet, so making any conclusions based on code size comparisions is quite 
ridiculous at this point.
The whole point of this patch was to demonstrate the algorithmic changes, 
not to demonstrate a final and perfectly tuned scheduler.

> > > so unmodified CFS is 4.6% faster on this box than with Roman's patch 
> > > and it's also more consistent/stable (10 times lower fluctuations).
> > 
> > Was SCHED_DEBUG enabled or disabled for these runs?
> 
> debugging disabled of course. (your patch has a self-validity checking 
> function [verify_queue()] that is called on SCHED_DEBUG=y, it would have 
> been unfair to test your patch with that included.)

I'll look into it next week.

bye, Roman

  reply	other threads:[~2007-09-02 17:16 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31  2:05 Roman Zippel
2007-08-31  9:36 ` Mike Galbraith
2007-08-31 13:22   ` Roman Zippel
2007-08-31 13:55     ` Mike Galbraith
2007-09-01  4:35     ` Mike Galbraith
2007-08-31 10:54 ` Ingo Molnar
2007-08-31 13:19   ` Roman Zippel
2007-09-02  9:26     ` Ingo Molnar
2007-09-03  2:58       ` Roman Zippel
2007-09-06  3:03         ` Syren Baran
2007-09-01  6:48   ` Roman Zippel
2007-09-02  2:19     ` Bill Davidsen
2007-09-02 17:02       ` Roman Zippel
2007-09-02  0:52 ` Daniel Walker
2007-09-02  7:20   ` Ingo Molnar
2007-09-02  8:40     ` Satyam Sharma
2007-09-02  9:59       ` Ingo Molnar
2007-09-02 15:16     ` Roman Zippel
2007-09-02 15:29       ` Ingo Molnar
2007-09-02 17:16         ` Roman Zippel [this message]
2007-09-02 19:21           ` Ingo Molnar
2007-09-07 15:35     ` Roman Zippel
2007-09-08  7:56       ` Mike Galbraith
2007-09-08  8:23         ` Mike Galbraith
2007-09-10 23:23         ` Roman Zippel
2007-09-11  6:18           ` Mike Galbraith
2007-09-11 11:28             ` Roman Zippel
2007-09-02 14:47   ` Roman Zippel
2007-09-02 15:00     ` Daniel Walker
2007-09-03 18:20       ` Roman Zippel
2007-09-03 21:06         ` Daniel Walker

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=Pine.LNX.4.64.0709021903240.1817@scrub.home \
    --to=zippel@linux-m68k.org \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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 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®