linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Michal Hocko <mhocko@kernel.org>
Cc: Mel Gorman <mgorman@suse.de>, Joonsoo Kim <js1304@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] mm, compaction: allow compaction for GFP_NOFS requests
Date: Mon, 10 Oct 2016 08:44:33 +0200	[thread overview]
Message-ID: <84149b25-95f3-2ddc-8e67-c3b2114922cd@suse.cz> (raw)
In-Reply-To: <20161007092107.GJ18439@dhcp22.suse.cz>

On 10/07/2016 11:21 AM, Michal Hocko wrote:
> On Fri 07-10-16 10:15:07, Vlastimil Babka wrote:
>> On 10/07/2016 08:50 AM, Michal Hocko wrote:
>>> On Fri 07-10-16 07:27:37, Vlastimil Babka wrote:
> [...]
>>>> But make sure you don't break kcompactd and manual compaction from /proc, as
>>>> they don't currently set cc->gfp_mask. Looks like until now it was only used
>>>> to determine direct compactor's migratetype which is irrelevant in those
>>>> contexts.
>>>
>>> OK, I see. This is really subtle. One way to go would be to provide a
>>> fake gfp_mask for them. How does the following look to you?
>>
>> Looks OK. I'll have to think about the kcompactd case, as gfp mask implying
>> unmovable migratetype might restrict it without good reason. But that would
>> be separate patch anyway, yours doesn't change that (empty gfp_mask also
>> means unmovable migratetype) and that's good.
>
> OK, I see. A follow up patch would be really trivial AFAICS. Just add
> __GFP_MOVABLE to the mask. But I am not familiar with all these details
> enough to propose a patch with full description.

Hm, actually the migratetype only matters for async compaction, and 
kcompactd uses sync_light, so __GFP_MOVABLE will have no effect right now.

--
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>

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

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04  8:12 Michal Hocko
2016-10-04 20:32 ` Dave Chinner
2016-10-05 11:38   ` Michal Hocko
2016-10-06  2:11     ` Dave Chinner
2016-10-07 13:18       ` Michal Hocko
2016-10-13  0:29         ` Dave Chinner
2016-10-13  7:39           ` Michal Hocko
2016-10-13 11:04             ` Michal Hocko
2016-10-16 20:49               ` Dave Chinner
2016-10-17  8:22                 ` Michal Hocko
2016-10-18  6:24                   ` Dave Chinner
2016-10-18 12:29                     ` Michal Hocko
2016-10-07  5:27 ` Vlastimil Babka
2016-10-07  6:50   ` Michal Hocko
2016-10-07  8:15     ` Vlastimil Babka
2016-10-07  9:21       ` Michal Hocko
2016-10-10  6:44         ` Vlastimil Babka [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=84149b25-95f3-2ddc-8e67-c3b2114922cd@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=js1304@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@kernel.org \
    /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