[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180907131923.GB24106@hirez.programming.kicks-ass.net>
Date: Fri, 7 Sep 2018 15:19:23 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
Cc: Jirka Hladky <jhladky@...hat.com>,
Mel Gorman <mgorman@...hsingularity.net>,
Jakub Ra??ek <jracek@...hat.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
"kkolakow@...hat.com" <kkolakow@...hat.com>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [SCHEDULER] Performance drop in 4.19 compared to 4.18 kernel
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.
Powered by blists - more mailing lists