mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Mel Gorman <mgorman@suse.de>, Joonsoo Kim <js1304@gmail.com>,
	Dave Chinner <david@fromorbit.com>,
	linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm, compaction: allow compaction for GFP_NOFS requests
Date: Thu, 13 Oct 2016 08:22:38 +0200	[thread overview]
Message-ID: <20161013062238.GA21678@dhcp22.suse.cz> (raw)
In-Reply-To: <224e7340-411c-f0ea-a9b5-0191517fbf7d@suse.cz>

On Thu 13-10-16 08:19:53, Vlastimil Babka wrote:
> On 10/12/2016 01:47 PM, Michal Hocko wrote:
[...]
> Acked-by: Vlastimil Babka <vbabka@suse.cz>

Thanks!

> 
> Small nitpick below.
> 
> > @@ -1696,14 +1703,16 @@ enum compact_result try_to_compact_pages(gfp_t gfp_mask, unsigned int order,
> >  		unsigned int alloc_flags, const struct alloc_context *ac,
> >  		enum compact_priority prio)
> >  {
> > -	int may_enter_fs = gfp_mask & __GFP_FS;
> >  	int may_perform_io = gfp_mask & __GFP_IO;
> >  	struct zoneref *z;
> >  	struct zone *zone;
> >  	enum compact_result rc = COMPACT_SKIPPED;
> > 
> > -	/* Check if the GFP flags allow compaction */
> > -	if (!may_enter_fs || !may_perform_io)
> > +	/*
> > +	 * Check if the GFP flags allow compaction - GFP_NOIO is really
> > +	 * tricky context because the migration might require IO and
> 
> "and" ?

a leftover from a longer comment. s@ and@.@

Thanks for the review!
-- 
Michal Hocko
SUSE Labs

      reply	other threads:[~2016-10-13  6:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 11:47 Michal Hocko
2016-10-13  6:19 ` Vlastimil Babka
2016-10-13  6:22   ` Michal Hocko [this message]

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=20161013062238.GA21678@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=js1304@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=vbabka@suse.cz \
    /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®