From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Jirka Hladky <jhladky@redhat.com>,
Mel Gorman <mgorman@techsingularity.net>,
Jakub Ra??ek <jracek@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"kkolakow@redhat.com" <kkolakow@redhat.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [SCHEDULER] Performance drop in 4.19 compared to 4.18 kernel
Date: Fri, 7 Sep 2018 19:14:20 +0530 [thread overview]
Message-ID: <20180907134420.GD3995@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180907131923.GB24106@hirez.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> [2018-09-07 15:19:23]:
> On Fri, Sep 07, 2018 at 06:26:49PM +0530, Srikar Dronamraju wrote:
>
> > Can you please pick
> >
> >
> > 1. 69bb3230297e881c797bbc4b3dbf73514078bc9d sched/numa: Stop multiple tasks
> > from moving to the cpu at the same time
> > 2. dc62cfdac5e5b7a61cd8a2bd4190e80b9bb408fc sched/numa: Avoid task migration
> > for small numa improvement
> > 3. 76e18a67cdd9e3609716c8a074c03168734736f9 sched/numa: Pass destination cpu as
> > a parameter to migrate_task_rq
> > 4. 489c19b440ebdbabffe530b9a41389d0a8b315d9 sched/numa: Reset scan rate
> > whenever task moves across nodes
> > 5. b7e9ae1ae3825f35cd0f38f1f0c8e91ea145bc30 sched/numa: Limit the
> > conditions where scan period is reset
> >
> > from https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/commit/kernel/sched
>
> That is not a stable tree; the whole thing is re-generated from my quilt
> set every time I feel like it.
>
> It is likely those commit ids will no longer exist in a few hours.
>
Okay, I will forward the relevant mails to Jirka.
--
Thanks and Regards
Srikar Dronamraju
next prev parent reply other threads:[~2018-09-07 13:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-07 9:34 [SCHEDULER] Performance drop in 4.19 compared to 4.18 kernel Jirka Hladky
2018-09-07 12:56 ` Srikar Dronamraju
2018-09-07 13:19 ` Peter Zijlstra
2018-09-07 13:44 ` Srikar Dronamraju [this message]
2018-09-07 13:52 ` Peter Zijlstra
2018-09-09 14:03 ` Jirka Hladky
2018-09-14 14:50 ` Jirka Hladky
2018-09-17 13:06 ` Mel Gorman
2018-09-17 13:14 ` Jirka Hladky
2018-10-04 13:08 ` Jon Masters
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=20180907134420.GD3995@linux.vnet.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=jhladky@redhat.com \
--cc=jracek@redhat.com \
--cc=kkolakow@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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