[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181009063123.GA66632@gmail.com>
Date: Tue, 9 Oct 2018 08:31:23 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Mel Gorman <mgorman@...hsingularity.net>
Cc: Peter Zijlstra <peterz@...radead.org>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
LKML <linux-kernel@...r.kernel.org>,
Rik van Riel <riel@...riel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Linux-MM <linux-mm@...ck.org>
Subject: Re: [PATCH] mm,numa: Remove remaining traces of rate-limiting.
* Mel Gorman <mgorman@...hsingularity.net> wrote:
> On Sat, Oct 06, 2018 at 04:53:19PM +0530, Srikar Dronamraju wrote:
> > With Commit efaffc5e40ae ("mm, sched/numa: Remove rate-limiting of automatic
> > NUMA balancing migration"), we no more require migrate lock and its
> > initialization. Its redundant. Hence remove it.
> >
> > Signed-off-by: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
>
> Hi Ingo,
>
> Can this be sent with the rest of the patches that got merged for 4.19-rc7
> so they are more or less together? It's functionally harmless to delay
> until the 4.20 merge window but it's a bit untidy. The mistake was mine
> switching between a backport and mainline versions of the original patch.
>
> Thanks
Ok, agreed and done - I queued it up in sched/urgent.
Thanks,
Ingo
Powered by blists - more mailing lists