public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Quentin Perret <quentin.perret@arm.com>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>
Subject: Re: [PATCH] sched/fair: Introduce fits_capacity()
Date: Mon, 17 Jun 2019 17:02:04 +0200	[thread overview]
Message-ID: <20190617150204.GG3436@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190606025204.qe5v7j6fysjkgxc6@vireshk-i7>

On Thu, Jun 06, 2019 at 08:22:04AM +0530, Viresh Kumar wrote:
> Hmm, even if the values are same currently I am not sure if we want
> the same for ever. I will write a patch for it though, if Peter/Rafael
> feel the same as you.

Is it really the same variable or just two numbers that happen to be the
same?

  parent reply	other threads:[~2019-06-17 15:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04  7:01 [PATCH] sched/fair: Introduce fits_capacity() Viresh Kumar
2019-06-04 15:59 ` Peter Oskolkov
2019-06-06  2:54   ` Viresh Kumar
2019-06-05  9:16 ` Quentin Perret
2019-06-06  2:52   ` Viresh Kumar
2019-06-06  8:12     ` Quentin Perret
2019-06-17 15:02     ` Peter Zijlstra [this message]
2019-06-18  3:12       ` Viresh Kumar
2019-06-18  7:26         ` Rafael J. Wysocki
2019-06-18  7:47           ` Viresh Kumar
2019-06-18  8:10             ` Rafael J. Wysocki
2019-06-18  8:25               ` Quentin Perret
2019-06-18  8:36                 ` Rafael J. Wysocki
2019-06-18  9:02                   ` Quentin Perret
2019-06-18  8:22             ` Quentin Perret
2019-07-17 10:33 ` Viresh Kumar
2019-07-17 14:59   ` Peter Zijlstra
2019-07-25 16:19 ` [tip:sched/core] " tip-bot for Viresh Kumar

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=20190617150204.GG3436@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=quentin.perret@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