From: Mel Gorman <mgorman@techsingularity.net>
To: Ingo Molnar <mingo@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Rik van Riel <riel@surriel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH] mm,numa: Remove remaining traces of rate-limiting.
Date: Mon, 8 Oct 2018 18:01:49 +0100 [thread overview]
Message-ID: <20181008170149.GB5819@techsingularity.net> (raw)
In-Reply-To: <1538824999-31230-1-git-send-email-srikar@linux.vnet.ibm.com>
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@linux.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
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2018-10-08 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-06 11:23 [PATCH] mm,numa: Remove remaining traces of rate-limiting Srikar Dronamraju
2018-10-06 13:23 ` Mel Gorman
2018-10-08 17:01 ` Mel Gorman [this message]
2018-10-09 6:31 ` Ingo Molnar
2018-10-09 7:01 ` [tip:sched/urgent] mm, sched/numa: Remove remaining traces of NUMA rate-limiting tip-bot for Srikar Dronamraju
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=20181008170149.GB5819@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=srikar@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).