mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Parth Shah <parth@linux.ibm.com>
To: Patrick Bellasi <patrick.bellasi@matbug.net>,
	Dhaval Giani <dhaval.giani@oracle.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Josef Bacik <jbacik@fb.com>, Chris Hyser <chris.hyser@oracle.com>,
	riel@surriel.com
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Juri Lelli <juri.lelli@redhat.com>, Paul Turner <pjt@google.com>,
	Ben Segall <bsegall@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jonathan Corbet <corbet@lwn.net>
Subject: Re: Scheduler wakeup path tuning surface: Interface discussion
Date: Thu, 12 Nov 2020 11:43:46 +0530	[thread overview]
Message-ID: <5a1b78c0-f286-bfaf-55bf-132093801131@linux.ibm.com> (raw)
In-Reply-To: <87imfi2qbk.derkling@matbug.net>

I was analyzing LPC 2020 discussion regarding Latency-nice interface and
have below points to initiate further discussion:

1. There was consensus that having interface like "Latency-nice" to
provide scheduler hints about task latency requirement can be very useful.

2. There are two use-case regarding the change in the number of CPUs to
be searched in select_idle_cpu path:
- milli-seconds optimization: Perform more scans to find idle CPUs to
reduce latency in milliseconds
- micro-seconds optimization: Perform less searches and queue it to any
CPU when system is overloaded

Both these optimization are contradictory since one requires to reduce
search space for latency sensitive task while other wants to increase
it. Though we can think about tuning select_idle_cpu path by keeping
mask of idle CPUs or applying other tricks, it will always be a
trade-off to search more or less and that's where latency-nice like
attribute can be useful for task aware decisions.

3. Using range is non-deterministic, meaning it is difficult to classify
a task should be marked with value of -18 or -19 and there will be
non-deterministic impact on system performance between these values.

And that's where should we even think of using "Flags" or other type
instead of range where we just say if a task is latency-sensitive or not
and won't classify if a task is "relatively" latency-nice than others?


Best,
Parth

      parent reply	other threads:[~2020-11-12  6:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87v9kv2545.derkling@matbug.com>
     [not found] ` <87h7wd15v2.derkling@matbug.net>
     [not found]   ` <87imgrlrqi.derkling@matbug.net>
     [not found]     ` <87mu5sqwkt.derkling@matbug.net>
     [not found]       ` <87eer42clt.derkling@matbug.net>
2020-06-23  7:29         ` Scheduler wakeup path tuning surface: Use-Cases and Requirements Patrick Bellasi
2020-06-23  7:49           ` [SchedulerWakeupLatency] Per-task vruntime wakeup bonus Patrick Bellasi
2020-07-10 13:21             ` Vincent Guittot
2020-07-10 19:59               ` Patrick Bellasi
2020-07-13 12:59                 ` Vincent Guittot
2020-07-16 16:48                   ` Dietmar Eggemann
2020-07-17 12:20                     ` Vincent Guittot
2020-07-16 19:54                   ` Patrick Bellasi
2020-07-17 14:19                     ` Vincent Guittot
2020-07-09 12:07           ` [SchedulerTaskPacking] Small background task packing Parth Shah
2020-07-09 23:08             ` [SchedulerWakeupLatency] Skipping Idle Cores and CPU Search chris hyser
2020-07-20  8:47               ` Dietmar Eggemann
2020-07-22 18:56                 ` chris hyser
2020-07-20 15:20             ` [SchedulerTaskPacking] Small background task packing Vincent Guittot
2020-07-23  9:33               ` Parth Shah
2020-07-23  9:31           ` [SchedulerWakeupLatency] Skip energy aware task placement Dietmar Eggemann
2020-07-29 14:01             ` Quentin Perret
2020-11-12  6:13           ` Parth Shah [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=5a1b78c0-f286-bfaf-55bf-132093801131@linux.ibm.com \
    --to=parth@linux.ibm.com \
    --cc=bsegall@google.com \
    --cc=chris.hyser@oracle.com \
    --cc=corbet@lwn.net \
    --cc=dhaval.giani@oracle.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=jbacik@fb.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=patrick.bellasi@matbug.net \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=riel@surriel.com \
    --cc=tglx@linutronix.de \
    --cc=vincent.guittot@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®