mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Chen <hi3766691@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][ANNOUNCE]RIFS-ES Scheduling V1 release.
Date: Sun, 17 Jun 2012 08:24:45 +0200	[thread overview]
Message-ID: <1339914285.7349.75.camel@marge.simpson.net> (raw)
In-Reply-To: <CANQmPXip+fKaSYsKaY5TF3Rax=XFFgyh=+BY61snVsgpReL7RA@mail.gmail.com>

On Sun, 2012-06-17 at 01:18 +0800, Chen wrote:

> CFS is good with its beautiful design. But in my opinion i think the
> sleeper feature will destroy the beautiful design.

Destroys may be a bit strong, but it does have it's problems, one being:
as resource contention increases, so does total sleep.

It would be great to come up with a model that works as well at letting
light tasks compete without the downsides, but until that happens, this
model is better than none at all.  With no wakeup preemption model, the
scheduler is not fair to light tasks, a big hairy wart IMHO, which mars
the beauty more than sleep model "beauty marks" (ok, so they're warts).

"Beauty is in the eye of the beholder" and "Perfect is the enemy of
good" are both applicable.. as is "Math is hard, let's go shopping" :)

-Mike


  reply	other threads:[~2012-06-17  6:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-16 17:18 Chen
2012-06-17  6:24 ` Mike Galbraith [this message]
     [not found]   ` <CANQmPXiU_Pz2qZkisF34TBepbRW4iJ4ytLLfiEmuJpCHxUwWvA@mail.gmail.com>
2012-06-17  8:20     ` Chen
     [not found]       ` <4d5440bc-73bb-4c30-8571-bb7004fc5c4a@skytron.local>
2012-06-20 15:17         ` Unzustellbar: " Chen
2012-06-21 10:40           ` Chen
2012-06-17 22:24   ` Chen
2012-06-18  3:01     ` Vikram Dhillon
2012-06-18  6:28       ` Chen
2012-06-18 10:56         ` Chen
     [not found]           ` <CANQmPXiyrd9EU=K+6VmMf-fyt5sb7v4bUhyRameHt5OKWc8CKQ@mail.gmail.com>
2012-06-19 14:22             ` Chen

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=1339914285.7349.75.camel@marge.simpson.net \
    --to=efault@gmx.de \
    --cc=hi3766691@gmail.com \
    --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 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®