mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dietmar Eggemann <dietmar.eggemann@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	rjw@rjwysocki.net, Juri Lelli <juri.lelli@redhat.com>,
	Morten Rasmussen <Morten.Rasmussen@arm.com>,
	viresh kumar <viresh.kumar@linaro.org>,
	Valentin Schneider <valentin.schneider@arm.com>
Subject: Re: [PATCH 1/4 v4] sched/pelt: Move pelt related code in a dedicated file
Date: Sun, 15 Apr 2018 15:27:59 +0200	[thread overview]
Message-ID: <3dfcbb67-746f-87b5-6167-6e5e220c4a69@arm.com> (raw)
In-Reply-To: <CAKfTPtCp2Qy7pZoTQH-550pJ2DZqwR2aAzk0+2B5b8DOenU4uA@mail.gmail.com>

On 04/15/2018 02:16 PM, Vincent Guittot wrote:
> On 15 April 2018 at 13:58, Dietmar Eggemann <dietmar.eggemann@arm.com> wrote:
>> On 03/16/2018 12:25 PM, Vincent Guittot wrote:
>>>
>>> We want to track rt_rq's utilization as a part of the estimation of the
>>> whole rq's utilization. This is necessary because rt tasks can steal
>>> utilization to cfs tasks and make them lighter than they are.
>>> As we want to use the same load tracking mecanism for both and prevent
>>> useless dependency between cfs and rt code, pelt code is moved in a
>>> dedicated file.
>>
>>
>> This would mean that we introduce function calls into the cfs scheduler
>> fast-path, something we avoided so far (e.g. the cpu and frequency
>> invariance hooks). Are we OK with that?
>>
>> Quentin mentioned this already during v3 review back in December.
> 
> Yes and I hadn't seen any differences in the code size with the patch
> which should have been the case if inline function where replaced by
> function call

I see a diff (e.g. for arm64 defconfig):

6d626e0aaf91 - (HEAD -> tip/sched/core_rt_rq_util_tracking) sched/nohz: 
monitor rt utilization (2018-04-15 Vincent Guittot)
3111c6206f0c - cpufreq/schedutil: add rt utilization tracking 
(2018-04-15 Vincent Guittot)
62e103d266ed - sched/rt: add rt_rq utilization tracking (2018-04-15 
Vincent Guittot)
8f78fef6b1a2 - sched/pelt: Move pelt related code in a dedicated file 
(2018-04-15 Vincent Guittot)
31e77c93e432 - (tip/sched/core_rt_rq_util_tracking_base) sched/fair: 
Update blocked load when newly idle (2018-03-09 Vincent Guittot)

deggeman-mac:/opt/git/kernel_org:tip/sched/core_rt_rq_util_tracking$ 
size vmlinux
    text    data     bss     dec     hex filename
11286856        6154896  410296 17852048        1106690 vmlinux

versus:

31e77c93e432 - (HEAD -> tip/sched/core_rt_rq_util_tracking_base) 
sched/fair: Update blocked load when ne$
ly idle (2018-03-09 Vincent Guittot)

deggeman-mac:/opt/git/kernel_org:tip/sched/core_rt_rq_util_tracking_base$ 
size vmlinux
    text    data     bss     dec     hex filename 

11295048        6154896  410296 17860240        1108690 vmlinux

So I assume that in kernel/sched/fair.o:

U __update_load_avg_blocked_se
U __update_load_avg_cfs_rq
U __update_load_avg_se

are function calls now.

  reply	other threads:[~2018-04-15 13:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 11:25 [PATCH 0/4 v4] sched/rt: track rt rq utilization Vincent Guittot
2018-03-16 11:25 ` [PATCH 1/4 v4] sched/pelt: Move pelt related code in a dedicated file Vincent Guittot
2018-04-15 11:58   ` Dietmar Eggemann
2018-04-15 12:16     ` Vincent Guittot
2018-04-15 13:27       ` Dietmar Eggemann [this message]
2018-04-15 11:58   ` Dietmar Eggemann
2018-03-16 11:25 ` [PATCH 2/4 v4] sched/rt: add rt_rq utilization tracking Vincent Guittot
2018-04-14 10:05   ` Peter Zijlstra
2018-04-14 11:29     ` Vincent Guittot
2018-03-16 11:25 ` [PATCH 3/4 v4] cpufreq/schedutil: add rt " Vincent Guittot
2018-03-16 11:25 ` [PATCH 4/4 v4] sched/nohz: monitor rt utilization Vincent Guittot
2018-04-14 10:07 ` [PATCH 0/4 v4] sched/rt: track rt rq utilization Peter Zijlstra
2018-04-14 11:42   ` Vincent Guittot
2018-04-15 11:56 ` Dietmar Eggemann
2018-04-15 12:00   ` Vincent Guittot

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=3dfcbb67-746f-87b5-6167-6e5e220c4a69@arm.com \
    --to=dietmar.eggemann@arm.com \
    --cc=Morten.Rasmussen@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rjw@rjwysocki.net \
    --cc=valentin.schneider@arm.com \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.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®