All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Byungchul Park <byungchul.park@lge.com>
Cc: Morten Rasmussen <morten.rasmussen@arm.com>,
	mingo@kernel.org, peterz@infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched: let __sched_period() use rq's nr_running
Date: Mon, 13 Jul 2015 09:07:01 +0200	[thread overview]
Message-ID: <1436771221.6576.60.camel@gmail.com> (raw)
In-Reply-To: <20150713005639.GH31287@byungchulpark-X58A-UD3R>

On Mon, 2015-07-13 at 09:56 +0900, Byungchul Park wrote:

> and i agree with that it makes latency increase for non-grouped tasks.

It's not only a latency hit for the root group, it's across the board.

I suspect an overloaded group foo/bar/baz would prefer small slices over
a large wait as well. I certainly wouldn't want my root group taking the
potentially huge hits that come with stretching period to accommodate an
arbitrarily overloaded /foo/bar/baz.

	-Mike


  reply	other threads:[~2015-07-13  7:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-10  8:11 [PATCH v2] sched: let __sched_period() use rq's nr_running byungchul.park
2015-07-10 13:31 ` Morten Rasmussen
2015-07-13  0:56   ` Byungchul Park
2015-07-13  7:07     ` Mike Galbraith [this message]
2015-07-13  8:29       ` Byungchul Park
2015-07-13 10:22         ` Mike Galbraith
2015-07-13 11:07           ` Byungchul Park
2015-07-13 12:30             ` Mike Galbraith
2015-07-14  2:07               ` Byungchul Park
2015-07-14  2:30                 ` Mike Galbraith
2015-07-13  8:26 ` Peter Zijlstra
2015-07-13  9:25   ` Byungchul Park
2015-07-14  2:26     ` Byungchul Park
2015-07-14  9:26 ` Byungchul Park

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=1436771221.6576.60.camel@gmail.com \
    --to=umgwanakikbuti@gmail.com \
    --cc=byungchul.park@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=morten.rasmussen@arm.com \
    --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 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.