From: Oleg Drokin <green@linuxhacker.ru>
To: Dave Chinner <david@fromorbit.com>
Cc: Steven Whitehouse <swhiteho@redhat.com>,
cluster-devel@redhat.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [PATCH] gfs2: use __vmalloc GFP_NOFS for fs-related allocations.
Date: Mon, 2 Feb 2015 01:57:23 -0500 [thread overview]
Message-ID: <E68E8257-1CE5-4833-B751-26478C9818C7@linuxhacker.ru> (raw)
In-Reply-To: <20150202053708.GG4251@dastard>
Hello!
On Feb 2, 2015, at 12:37 AM, Dave Chinner wrote:
> On Sun, Feb 01, 2015 at 10:59:54PM -0500, green@linuxhacker.ru wrote:
>> From: Oleg Drokin <green@linuxhacker.ru>
>>
>> leaf_dealloc uses vzalloc as a fallback to kzalloc(GFP_NOFS), so
>> it clearly does not want any shrinker activity within the fs itself.
>> convert vzalloc into __vmalloc(GFP_NOFS|__GFP_ZERO) to better achieve
>> this goal.
>>
>> Signed-off-by: Oleg Drokin <green@linuxhacker.ru>
>> ---
>> fs/gfs2/dir.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/gfs2/dir.c b/fs/gfs2/dir.c
>> index c5a34f0..6371192 100644
>> --- a/fs/gfs2/dir.c
>> +++ b/fs/gfs2/dir.c
>> @@ -1896,7 +1896,8 @@ static int leaf_dealloc(struct gfs2_inode *dip, u32 index, u32 len,
>>
>> ht = kzalloc(size, GFP_NOFS | __GFP_NOWARN);
>> if (ht == NULL)
>> - ht = vzalloc(size);
>> + ht = __vmalloc(size, GFP_NOFS | __GFP_NOWARN | __GFP_ZERO,
>> + PAGE_KERNEL);
> That, in the end, won't help as vmalloc still uses GFP_KERNEL
> allocations deep down in the PTE allocation code. See the hacks in
> the DM and XFS code to work around this. i.e. go look for callers of
> memalloc_noio_save(). It's ugly and grotesque, but we've got no
> other way to limit reclaim context because the MM devs won't pass
> the vmalloc gfp context down the stack to the PTE allocations....
Hm, interesting.
So all the other code in the kernel that does this sort of thing (and there's quite a bit
outside of xfs and ocfs2) would not get the desired effect?
So, I did some digging in archives and found this thread from 2010 onward with various
patches and rants.
Not sure how I missed that before.
Should we have another run at this I wonder?
Bye,
Oleg
next prev parent reply other threads:[~2015-02-02 6:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 3:59 green
2015-02-02 5:37 ` Dave Chinner
2015-02-02 6:57 ` Oleg Drokin [this message]
2015-02-02 8:11 ` Dave Chinner
2015-02-02 10:30 ` Steven Whitehouse
2015-02-03 22:33 ` Dave Chinner
2015-02-04 7:13 ` Oleg Drokin
2015-02-04 9:49 ` Steven Whitehouse
2015-02-05 20:11 ` Dave Chinner
2015-02-05 11:45 ` Dave Chinner
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=E68E8257-1CE5-4833-B751-26478C9818C7@linuxhacker.ru \
--to=green@linuxhacker.ru \
--cc=cluster-devel@redhat.com \
--cc=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=swhiteho@redhat.com \
/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
all inboxes | Powered by JetHome®