All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: ck@vds.kolivas.org,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [ck] Re: kernel scedular
Date: Wed, 13 Jun 2007 13:36:16 +1000	[thread overview]
Message-ID: <466F6630.2050207@yahoo.com.au> (raw)
In-Reply-To: <200706121925.02286.Martin@lichtvoll.de>

Martin Steigerwald wrote:
> Am Sonntag 10 Juni 2007 schrieb Linus Torvalds:
> 
> Hi Linus!
> 
> 
>>Ehh.. It was tested extensively by lots of people. It was in -mm for a
>>while, and yes, there have been tons of people testing both. I've
>>followed it, and it seems fair to say that yes, Ingo took a lot of
>>ideas from SD, but CFS seems to have gotten more people involved, and
>>we had several people compare the two, and CFS was generally better.
> 
> 
> Well actually I did not see that general result yet. I have seen quite 
> some testings and quite some reports on the ck patch mailinglist also 
> where in favor of SD. If it matters I will collect those, but I think 
> Ingo already did include most of them in his summary.

I'd just like to say that last time I tested CFS it was very slow
on context switching. I don't know if this has been improved, but I
think it should be.

I'm not talking about context switching with heaps of tasks, but
about lmbench 2-task ping pongs and such.

Also it used pretty small timeslices to achieve interactivity, which
didn't seem like a good idea. I wonder if that's been fixed?

-- 
SUSE Labs, Novell Inc.

      parent reply	other threads:[~2007-06-13  3:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <466B45D3.3020104@gmail.com>
     [not found] ` <alpine.LFD.0.98.0706091731020.20321@woody.linux-foundation.org>
2007-06-12 17:24   ` [ck] Re: kernel scedular Martin Steigerwald
2007-06-12 17:37     ` Martin Steigerwald
2007-06-13  3:36     ` Nick Piggin [this message]

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=466F6630.2050207@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=Martin@lichtvoll.de \
    --cc=ck@vds.kolivas.org \
    --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.