From: Rohit Jain <rohit.k.jain@oracle.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Joel Fernandes <joel.opensrc@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Valentin Schneider <valentin.schneider@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Quentin Perret <quentin.perret@arm.com>,
Joel Fernandes <joelaf@google.com>
Subject: Re: [PATCH] sched/fair: Rearrange select_task_rq_fair() to optimize it
Date: Wed, 25 Apr 2018 09:48:50 -0700 [thread overview]
Message-ID: <e20035ba-8d1f-bee9-f817-d9f514ee0326@oracle.com> (raw)
In-Reply-To: <20180425025111.zn6fwkr4o4d3y52c@vireshk-i7>
On 04/24/2018 07:51 PM, Viresh Kumar wrote:
> On 24-04-18, 15:34, Rohit Jain wrote:
>> Including the "unlikely" suggestion and the original patch, as expected
>> with a quick hackbench test on a 44 core 2 socket x86 machine causes no
>> change in performance.
> Want me to include your Tested-by in next version ?
>
Please feel free to include it.
I was not sure if this is too small a test to say tested by.
next prev parent reply other threads:[~2018-04-25 16:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-23 10:38 [PATCH] sched/fair: Rearrange select_task_rq_fair() to optimize it Viresh Kumar
2018-04-24 10:02 ` Valentin Schneider
2018-04-24 10:30 ` Viresh Kumar
2018-04-24 10:43 ` Peter Zijlstra
2018-04-24 11:19 ` Valentin Schneider
2018-04-24 12:35 ` Peter Zijlstra
2018-04-24 15:46 ` Joel Fernandes
2018-04-24 15:47 ` Joel Fernandes
2018-04-24 22:34 ` Rohit Jain
2018-04-25 2:51 ` Viresh Kumar
2018-04-25 16:48 ` Rohit Jain [this message]
2018-04-25 5:15 ` Viresh Kumar
2018-04-25 8:13 ` Quentin Perret
2018-04-25 9:03 ` Viresh Kumar
2018-04-25 9:39 ` Quentin Perret
2018-04-25 10:13 ` Viresh Kumar
2018-04-25 10:55 ` Quentin Perret
2018-04-25 8:12 ` Quentin Perret
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=e20035ba-8d1f-bee9-f817-d9f514ee0326@oracle.com \
--to=rohit.k.jain@oracle.com \
--cc=daniel.lezcano@linaro.org \
--cc=joel.opensrc@gmail.com \
--cc=joelaf@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=quentin.perret@arm.com \
--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 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.