mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yisheng Xie <xieyisheng1@huawei.com>
To: Vlastimil Babka <vbabka@suse.cz>, <akpm@linux-foundation.org>,
	<mhocko@suse.com>, <mgorman@techsingularity.net>,
	<iamjoonsoo.kim@lge.com>, <rientjes@google.com>,
	<minchan@kernel.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
	<guohanjun@huawei.com>, <qiuxishi@huawei.com>,
	<liubo95@huawei.com>
Subject: Re: [RFC] mm/compaction: ignore block suitable after check large free page
Date: Fri, 10 Mar 2017 17:53:58 +0800	[thread overview]
Message-ID: <9104271f-c90f-772c-26b2-410fa8bdfdb0@huawei.com> (raw)
In-Reply-To: <eb3bbece-77ea-b88f-d4bf-dbf9bdf7f413@suse.cz>

Hi Vlastimil,

Thanks for comment.
On 2017/3/10 15:30, Vlastimil Babka wrote:
> On 03/10/2017 05:20 AM, Yisheng Xie wrote:
>> If the migrate target is a large free page and we ignore suitable,
>> it may not good for defrag. So move the ignore block suitable after
>> check large free page.
> 
> Right. But in practice I expect close to no impact, because direct
> compaction shouldn't have to be called if there's a >=pageblock_order
> page already available.
> 
Maybe you are right and this change is just based on logical analyses.

Presently, only in direct compaction, we increase the compaction priority,
and ignore suitable at MIN_COMPACT_PRIORITY. I have a silly question, can
we do the similar thing in kcompactd? maybe by doing most work in kcompactd,
we can get better perf of slow path.

Thanks
Yisheng Xie

>> Signed-off-by: Yisheng Xie <xieyisheng1@huawei.com>
>> ---
>>  mm/compaction.c | 6 +++---
>>  1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/mm/compaction.c b/mm/compaction.c
>> index 0fdfde0..4bf2a5d 100644
>> --- a/mm/compaction.c
>> +++ b/mm/compaction.c
>> @@ -991,9 +991,6 @@ static bool too_many_isolated(struct zone *zone)
>>  static bool suitable_migration_target(struct compact_control *cc,
>>  							struct page *page)
>>  {
>> -	if (cc->ignore_block_suitable)
>> -		return true;
>> -
>>  	/* If the page is a large free page, then disallow migration */
>>  	if (PageBuddy(page)) {
>>  		/*
>> @@ -1005,6 +1002,9 @@ static bool suitable_migration_target(struct compact_control *cc,
>>  			return false;
>>  	}
>>  
>> +	if (cc->ignore_block_suitable)
>> +		return true;
>> +
>>  	/* If the block is MIGRATE_MOVABLE or MIGRATE_CMA, allow migration */
>>  	if (migrate_async_suitable(get_pageblock_migratetype(page)))
>>  		return true;
>>
> 
> 
> .
> 

  reply	other threads:[~2017-03-10  9:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-10  4:20 Yisheng Xie
2017-03-10  7:30 ` Vlastimil Babka
2017-03-10  9:53   ` Yisheng Xie [this message]
2017-03-13  9:51     ` Vlastimil Babka
2017-03-13 12:16       ` Yisheng Xie

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=9104271f-c90f-772c-26b2-410fa8bdfdb0@huawei.com \
    --to=xieyisheng1@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=guohanjun@huawei.com \
    --cc=iamjoonsoo.kim@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liubo95@huawei.com \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=qiuxishi@huawei.com \
    --cc=rientjes@google.com \
    --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®