From: Mike Galbraith <efault@gmx.de>
To: Naoaki MAEDA <maeda.naoaki@gmail.com>
Cc: MAEDA Naoaki <maeda.naoaki@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, ckrm-tech@lists.sourceforge.net
Subject: Re: [ckrm-tech] Re: [RFC][PATCH 3/9] CPU controller - Adds timeslice scaling
Date: Fri, 21 Apr 2006 14:03:49 +0200 [thread overview]
Message-ID: <1145621030.7614.44.camel@homer> (raw)
In-Reply-To: <9fe69740604210450h798eded8nff1ef8b98c0f151@mail.gmail.com>
On Fri, 2006-04-21 at 20:50 +0900, Naoaki MAEDA wrote:
> It was not good explanation. Let me restate that.
> The effect of shortening timeslice is to let the task be expired soon
> by shortening
> its remainder timeclice, so it still works even if the task consome very small
> timeslice at one time. However, expired TASK_INTERACTIVE tasks will be requeued
> to the active for a while by the scheduler, so shortening timeslice
> doesn't work well for
> TASK_INTERACTIVE tasks.
Yeah, understood. This shortening of timeslice I think is generally
bad, (hmm...) though in an environment where preemption is rampant, this
shortening of slice should lead to a throughput gain for low ranking
_interdependent_ tasks. Is that what you're trying to accomplish? To
reduce latency at the bottom in the face of preemption from above?
-Mike
next prev parent reply other threads:[~2006-04-21 12:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 2:27 [RFC][PATCH 0/9] CKRM CPU resource controller maeda.naoaki
2006-04-21 2:27 ` [RFC][PATCH 1/9] CPU controller - Adds class load estimation maeda.naoaki
2006-04-21 2:27 ` [RFC][PATCH 2/9] CPU controller - Adds class hungry detection maeda.naoaki
2006-04-21 2:27 ` [RFC][PATCH 3/9] CPU controller - Adds timeslice scaling maeda.naoaki
2006-04-21 8:17 ` Mike Galbraith
2006-04-21 8:56 ` MAEDA Naoaki
2006-04-21 11:50 ` [ckrm-tech] " Naoaki MAEDA
2006-04-21 12:03 ` Mike Galbraith [this message]
2006-04-21 11:53 ` Mike Galbraith
2006-04-21 2:27 ` [RFC][PATCH 4/9] CPU controller - Adds interface functions maeda.naoaki
2006-04-21 2:27 ` [RFC][PATCH 5/9] CPU controller - Documents how the controller works maeda.naoaki
2006-04-23 7:13 ` Mike Galbraith
2006-04-24 6:25 ` [ckrm-tech] " MAEDA Naoaki
2006-04-24 9:49 ` Mike Galbraith
2006-04-21 2:27 ` [RFC][PATCH 6/9] CPU controller - Adds basic functions and registering the controller maeda.naoaki
2006-04-21 2:28 ` [RFC][PATCH 7/9] CPU controller - Adds routines to change share values and show stat maeda.naoaki
2006-04-21 2:28 ` [RFC][PATCH 8/9] CPU controller - Adds cpu hotplug notifier maeda.naoaki
2006-04-21 2:28 ` [RFC][PATCH 9/9] CPU controller - Documents how to use the controller maeda.naoaki
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=1145621030.7614.44.camel@homer \
--to=efault@gmx.de \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maeda.naoaki@gmail.com \
--cc=maeda.naoaki@jp.fujitsu.com \
/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.