[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20180717125059.GC30926@dhcp22.suse.cz>
Date: Tue, 17 Jul 2018 14:50:59 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Steven Whitehouse <swhiteho@...hat.com>
Cc: LKML <linux-kernel@...r.kernel.org>,
Artem Bityutskiy <dedekind1@...il.com>,
Richard Weinberger <richard@....at>,
David Woodhouse <dwmw2@...radead.org>,
Brian Norris <computersforpeace@...il.com>,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
Marek Vasut <marek.vasut@...il.com>,
Cyrille Pitchen <cyrille.pitchen@...ev4u.fr>,
Theodore Ts'o <tytso@....edu>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Bob Peterson <rpeterso@...hat.com>,
Trond Myklebust <trond.myklebust@...marydata.com>,
Anna Schumaker <anna.schumaker@...app.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Philippe Ombredanne <pombredanne@...b.com>,
Kate Stewart <kstewart@...uxfoundation.org>,
Mikulas Patocka <mpatocka@...hat.com>,
linux-mtd@...ts.infradead.org, linux-ext4@...r.kernel.org,
cluster-devel@...hat.com, linux-nfs@...r.kernel.org,
linux-mm@...ck.org
Subject: Re: vmalloc with GFP_NOFS
On Tue 24-04-18 14:09:27, Michal Hocko wrote:
> On Tue 24-04-18 20:26:23, Steven Whitehouse wrote:
> [...]
> > It would be good to fix this, and it has been known as an issue for a long
> > time. We might well be able to make use of the new API though. It might be
> > as simple as adding the calls when we get & release glocks, but I'd have to
> > check the code to be sure,
>
> Yeah, starting with annotating those locking contexts and how document
> how their are used in the reclaim is the great first step. This has to
> be done per-fs obviously.
Any chance of progress here?
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists