From: Michal Hocko <mhocko@kernel.org>
To: linux-mm@kvack.org
Cc: Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, Tejun Heo <tj@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [RFC 0/2] do not depend on cpuhotplug logs in lru_add_drain_all
Date: Thu, 2 Nov 2017 10:36:11 +0100 [thread overview]
Message-ID: <20171102093613.3616-1-mhocko@kernel.org> (raw)
Hi,
this is an RFC to drop get_online_cpus from lru_add_drain_all ad this
has caused a very subtle lockdep splats recently [1]. I didn't get even
to properly test this yet and I am sending it early to check whether the
thinking behind is sound. I am basically following the same pattern we
have used for removing get_online_cpus from drain_all_pages which should
be the similar case.
Does anybody see any obvious problem?
[1] http://lkml.kernel.org/r/089e0825eec8955c1f055c83d476@google.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-11-02 9:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-02 9:36 Michal Hocko [this message]
2017-11-02 9:36 ` [PATCH 1/2] shmem: drop lru_add_drain_all from shmem_wait_for_pins Michal Hocko
2017-11-03 7:46 ` Hugh Dickins
2017-11-03 8:24 ` Michal Hocko
2017-11-03 9:52 ` David Herrmann
2017-11-05 0:28 ` Hugh Dickins
2017-11-05 7:37 ` Michal Hocko
2017-11-02 9:36 ` [PATCH 2/2] mm: drop hotplug lock from lru_add_drain_all Michal Hocko
2017-11-02 12:37 ` Michal Hocko
2017-11-02 13:02 ` Thomas Gleixner
2017-11-02 13:16 ` Michal Hocko
2017-11-02 13:42 ` Thomas Gleixner
2017-11-03 20:02 ` kbuild test robot
2017-11-05 7:45 ` [PATCH -v2] " Michal Hocko
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=20171102093613.3616-1-mhocko@kernel.org \
--to=mhocko@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.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;
as well as URLs for NNTP newsgroup(s).