From: Michal Hocko <mhocko@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: get rid of __alloc_pages_high_priority
Date: Fri, 13 Nov 2015 10:16:51 +0100 [thread overview]
Message-ID: <20151113091651.GA2632@dhcp22.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.10.1511121245430.10324@chino.kir.corp.google.com>
On Thu 12-11-15 12:47:45, David Rientjes wrote:
> On Thu, 12 Nov 2015, mhocko@kernel.org wrote:
[...]
> > Hi,
> > I think that this is more a cleanup than any functional change. We
> > are rarely screwed so much that __alloc_pages_high_priority would
> > fail. Yet I think that __alloc_pages_high_priority is obscuring the
> > overal intention more than it is helpful. Another motivation is to
> > reduce wait_iff_congested call to a single one in the allocator. I plan
> > to do other changes in that area and get rid of it altogether.
>
> I think it's a combination of a cleanup (the inlining of
> __alloc_pages_high_priority) and a functional change (no longer looping
> infinitely around a get_page_from_freelist() call). I'd suggest doing the
> inlining in one patch and then the reworking of __GFP_NOFAIL when
> ALLOC_NO_WATERMARKS fails just so we could easily revert the latter if
> necessary.
I can split it up if this is really preferable of course.
--
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:[~2015-11-13 9:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 15:53 [PATCH] mm: get rid of __alloc_pages_high_priority mhocko
2015-11-12 20:47 ` David Rientjes
2015-11-13 9:16 ` Michal Hocko [this message]
2015-11-13 22:31 ` David Rientjes
2015-11-13 10:18 ` Mel Gorman
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=20151113091651.GA2632@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=rientjes@google.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;
as well as URLs for NNTP newsgroup(s).