From: preeti <preeti@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: peterz@infradead.org, svaidy@linux.vnet.ibm.com, pjt@google.com
Subject: Re: [RFC PATCH 2/2] sched:Pick the apt busy sched group during load balancing
Date: Fri, 12 Oct 2012 10:46:28 +0530 [thread overview]
Message-ID: <5077A7AC.3090905@linux.vnet.ibm.com> (raw)
In-Reply-To: <20121012045047.18271.11550.stgit@preeti.in.ibm.com>
Hi everyone,
The figures SCHED_GRP1:3200 and SCHED_GRP2:1156 shown below in the
changelog is the probable figure as calculated with the per-entity-
load-tracking metric for the runqueue load.
> If a sched group has passed the test for sufficient load in
> update_sg_lb_stats,to qualify for load balancing,then PJT's
> metrics has to be used to qualify the right sched group as the busiest group.
>
> The scenario which led to this patch is shown below:
> Consider Task1 and Task2 to be a long running task
> and Tasks 3,4,5,6 to be short running tasks
>
> Task3
> Task4
> Task1 Task5
> Task2 Task6
> ------ ------
> SCHED_GRP1 SCHED_GRP2
>
> Normal load calculator would qualify SCHED_GRP2 as
> the candidate for sd->busiest due to the following loads
> that it calculates.
>
> SCHED_GRP1:2048
> SCHED_GRP2:4096
>
> Load calculator would probably qualify SCHED_GRP1 as the candidate
> for sd->busiest due to the following loads that it calculates
>
> SCHED_GRP1:3200
> SCHED_GRP2:1156
>
Regards
Preeti
next prev parent reply other threads:[~2012-10-12 5:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 4:50 [RFC PATCH 0/2] sched: Load Balancing using Per-entity-Load-tracking Preeti U Murthy
2012-10-12 4:50 ` [RFC PATCH 1/2] sched:Prevent movement of short running tasks during load balancing Preeti U Murthy
2012-10-12 4:50 ` [RFC PATCH 2/2] sched:Pick the apt busy sched group " Preeti U Murthy
2012-10-12 5:16 ` preeti [this message]
2012-10-15 9:14 ` [RFC PATCH 0/2] sched: Load Balancing using Per-entity-Load-tracking preeti
2012-10-17 12:20 ` preeti
2012-10-18 17:26 ` Morten Rasmussen
2012-10-19 4:17 ` preeti
2012-10-19 4:17 ` preeti
2012-10-19 4:57 ` preeti
2012-10-19 4:57 ` preeti
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=5077A7AC.3090905@linux.vnet.ibm.com \
--to=preeti@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=svaidy@linux.vnet.ibm.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.