public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Gaurav Poothia <gaurav.poothia@gmail.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org, mingo@redhat.com
Subject: Re: Question about group scheduler cpu shares
Date: Fri, 22 Jul 2016 06:19:13 +0200	[thread overview]
Message-ID: <1469161153.3862.62.camel@gmail.com> (raw)
In-Reply-To: <CADDfC=p-kyGbOzZWJQaaHhshB35NtwZig0ok9HRiWkhBritfBA@mail.gmail.com>

On Thu, 2016-07-21 at 20:24 -0700, Gaurav Poothia wrote:

(top posting.. naught naughty;)

> 1.What is the function that translates from various nice levels to
> weight i.e. nice(0) == 1024 how to translate for other levels

If you rummage around in kernel/sched, you'll find this table:

const int sched_prio_to_weight[40] = {
 /* -20 */     88761,     71755,     56483,     46273,     36291,
 /* -15 */     29154,     23254,     18705,     14949,     11916,
 /* -10 */      9548,      7620,      6100,      4904,      3906,
 /*  -5 */      3121,      2501,      1991,      1586,      1277,
 /*   0 */      1024,       820,       655,       526,       423,
 /*   5 */       335,       272,       215,       172,       137,
 /*  10 */       110,        87,        70,        56,        45,
 /*  15 */        36,        29,        23,        18,        15,
};

> 2.How does that work when an interior node has multiple tasks? So if I
> added tasks E and F with difference nice levels to Group 1 task list
> how would the math work?

The math works the same as if you were adding task groups.  An entity
is an entity is an entity...

	-Mike

      reply	other threads:[~2016-07-22  4:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-21 19:03 Question about group scheduler cpu shares Gaurav Poothia
2016-07-22  1:18 ` Gaurav Poothia
2016-07-22  2:51   ` Mike Galbraith
2016-07-22  3:24     ` Gaurav Poothia
2016-07-22  4:19       ` Mike Galbraith [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=1469161153.3862.62.camel@gmail.com \
    --to=umgwanakikbuti@gmail.com \
    --cc=gaurav.poothia@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox