From: Michal Hocko <mhocko@kernel.org>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Linux MM <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
David Rientjes <rientjes@google.com>,
Mel Gorman <mgorman@suse.de>,
Johannes Weiner <hannes@cmpxchg.org>,
Anatoly Stepanov <astepanov@cloudlinux.com>,
LKML <linux-kernel@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Mike Snitzer <snitzer@redhat.com>,
dm-devel@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>,
Theodore Ts'o <tytso@mit.edu>,
kvm@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org,
Dave Chinner <david@fromorbit.com>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [RFC PATCH] mm: introduce kv[mz]alloc helpers
Date: Wed, 14 Dec 2016 10:05:02 +0100 [thread overview]
Message-ID: <20161214090502.GC25573@dhcp22.suse.cz> (raw)
In-Reply-To: <C2C892CD-BAF7-4E72-927D-B79D95A9B7FA@dilger.ca>
On Tue 13-12-16 13:55:46, Andreas Dilger wrote:
> On Dec 13, 2016, at 3:14 AM, Michal Hocko <mhocko@kernel.org> wrote:
> >
> > Are there any more comments or objections to this patch? Is this a good
> > start or kv[mz]alloc has to provide a way to cover GFP_NOFS users as
> > well in the initial version.
>
> I'm in favour of this cleanup as a starting point. I definitely agree
> that this same functionality is in use in a number of places and should
> be consolidated.
>
> The vmalloc() from GFP_NOFS can be addressed separately in later patches.
> That is an issue for several filesystems, and while XFS works around this,
> it would be better to lift that out of the filesystem code into the VM.
Well, my longer term plan is to change how GFP_NOFS is used from the fs
code rather than tweak the VM layer. The current situation with the nofs
is messy and confusing. In many contexts it is used without a good
reason - just to be sure that nothing will break. I strongly believe
that we should use a scope api [1] which marks whole regions of
potentially reclaim dangerous code paths and all the allocations within
that region will inherit the nofs protection automatically. That would
solve the vmalloc(GFP_NOFS) problem as well. The route to get there is
no short or easy. I am planning to repost the scope patchset hopefully
soon with ext4 converted.
[1] http://lkml.kernel.org/r/1461671772-1269-1-git-send-email-mhocko@kernel.org
> Really, there are several of things about vmalloc() that could improve
> if we decided to move it out of the dog house and allow it to become a
> first class citizen, but that needs a larger discussion, and you can
> already do a lot of cleanup with just the introduction of kvmalloc().
>
> Since this is changing the ext4 code, you can add my:
>
> Reviewed-by: Andreas Dilger <adilger@dilger.ca>
thanks!
--
Michal Hocko
SUSE Labs
--
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 prev parent reply other threads:[~2016-12-14 9:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 10:33 [RFC PATCH] mm: introduce kv[mz]alloc helpers Michal Hocko
2016-12-08 13:00 ` David Hildenbrand
2016-12-08 13:51 ` Michal Hocko
2016-12-09 1:44 ` Dave Chinner
2016-12-09 2:00 ` Al Viro
2016-12-09 6:22 ` Michal Hocko
2016-12-09 6:38 ` Al Viro
2016-12-09 6:51 ` Michal Hocko
2016-12-09 6:18 ` Michal Hocko
2016-12-13 10:14 ` Michal Hocko
2016-12-13 20:55 ` Andreas Dilger
2016-12-14 9:05 ` Michal Hocko [this message]
2016-12-13 22:07 ` Joe Perches
2016-12-14 8:59 ` Michal Hocko
2016-12-20 13:50 ` Michal Hocko
2016-12-20 17:38 ` Joe Perches
2016-12-20 22:13 ` Andrew Morton
[not found] ` <20161221065922.GB16502@dhcp22.suse.cz>
2016-12-21 8:45 ` 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=20161214090502.GC25573@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=adilger@dilger.ca \
--cc=akpm@linux-foundation.org \
--cc=astepanov@cloudlinux.com \
--cc=david@fromorbit.com \
--cc=dm-devel@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=kvm@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rientjes@google.com \
--cc=snitzer@redhat.com \
--cc=tytso@mit.edu \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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).