From: Michal Hocko <mhocko@kernel.org>
To: Steven Whitehouse <swhiteho@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Artem Bityutskiy <dedekind1@gmail.com>,
Richard Weinberger <richard@nod.at>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Marek Vasut <marek.vasut@gmail.com>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Theodore Ts'o <tytso@mit.edu>,
Andreas Dilger <adilger.kernel@dilger.ca>,
Bob Peterson <rpeterso@redhat.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <anna.schumaker@netapp.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Philippe Ombredanne <pombredanne@nexb.com>,
Kate Stewart <kstewart@linuxfoundation.org>,
Mikulas Patocka <mpatocka@redhat.com>,
linux-mtd@lists.infradead.org, linux-ext4@vger.kerne
Subject: Re: vmalloc with GFP_NOFS
Date: Tue, 24 Apr 2018 14:09:27 -0600 [thread overview]
Message-ID: <20180424200927.GU17484@dhcp22.suse.cz> (raw)
In-Reply-To: <ce42f323-870c-21df-ac27-1bec6aa7e5d1@redhat.com>
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.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-04-24 20:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 16:27 vmalloc with GFP_NOFS Michal Hocko
2018-04-24 16:46 ` Mikulas Patocka
2018-04-24 16:55 ` Michal Hocko
2018-04-24 17:05 ` Mikulas Patocka
2018-04-24 18:35 ` Theodore Y. Ts'o
2018-04-24 19:25 ` Michal Hocko
2018-05-09 13:42 ` Michal Hocko
2018-05-09 14:13 ` David Sterba
2018-05-09 15:13 ` Darrick J. Wong
2018-05-09 16:24 ` Mike Rapoport
2018-05-09 21:06 ` Michal Hocko
2018-05-09 21:04 ` Michal Hocko
2018-05-09 22:02 ` Darrick J. Wong
2018-05-10 5:58 ` Michal Hocko
2018-05-10 7:18 ` Michal Hocko
2018-07-17 12:49 ` Michal Hocko
2018-04-24 19:03 ` Richard Weinberger
2018-04-24 19:28 ` Michal Hocko
2018-04-24 22:18 ` Richard Weinberger
2018-04-24 23:09 ` Michal Hocko
2018-04-24 23:17 ` Mikulas Patocka
2018-04-24 23:25 ` Michal Hocko
2018-04-25 12:43 ` Mikulas Patocka
2018-04-25 14:45 ` Michal Hocko
2018-04-25 15:25 ` Mikulas Patocka
2018-04-25 16:56 ` Michal Hocko
2018-07-17 12:47 ` Michal Hocko
2018-04-24 19:05 ` Richard Weinberger
2018-04-24 19:10 ` Richard Weinberger
2018-04-24 19:26 ` Steven Whitehouse
2018-04-24 20:09 ` Michal Hocko [this message]
2018-07-17 12:50 ` 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=20180424200927.GU17484@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=adrian.hunter@intel.com \
--cc=anna.schumaker@netapp.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-ext4@vger.kerne \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mpatocka@redhat.com \
--cc=pombredanne@nexb.com \
--cc=richard@nod.at \
--cc=rpeterso@redhat.com \
--cc=swhiteho@redhat.com \
--cc=trond.myklebust@primarydata.com \
--cc=tytso@mit.edu \
/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).