All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Gioh Kim <gioh.kim@lge.com>,
	akpm@linux-foundation.org, rientjes@google.com,
	iamjoonsoo.kim@lge.com, mgorman@suse.de
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, gunho.lee@lge.com
Subject: Re: [PATCH] [RFC] mm/compaction: initialize compaction information
Date: Fri, 20 Mar 2015 08:51:31 +0100	[thread overview]
Message-ID: <550BD183.5020005@suse.cz> (raw)
In-Reply-To: <550B5CD1.5010306@lge.com>

On 03/20/2015 12:33 AM, Gioh Kim wrote:
>>> diff --git a/mm/compaction.c b/mm/compaction.c
>>> index 8c0d945..827ec06 100644
>>> --- a/mm/compaction.c
>>> +++ b/mm/compaction.c
>>> @@ -1587,8 +1587,10 @@ static void __compact_pgdat(pg_data_t *pgdat, struct compact_control *cc)
>>>                    INIT_LIST_HEAD(&cc->freepages);
>>>                    INIT_LIST_HEAD(&cc->migratepages);
>>>
>>> -               if (cc->order == -1 || !compaction_deferred(zone, cc->order))
>>> +               if (cc->order == -1 || !compaction_deferred(zone, cc->order)) {
>>> +                       __reset_isolation_suitable(zone);
>>
>> This will also trigger reset when called from kswapd through compact_pgdat() and
>> !compaction_deferred() is true.
>> The reset should be restricted to cc->order == -1 which only happens from /proc
>> trigger.
>>
>>>                            compact_zone(zone, cc);
>>> +               }
>>>
>>>                    if (cc->order > 0) {
>>>                            if (zone_watermark_ok(zone, cc->order,
>>>
>>
>>
>
> I've not been familiar with compaction code.
> I think cc->order is -1 only if __compact_pgdat is called via /proc.

Yes that's what I meant.

> This is ugly but I don't have better solution.
> Do you have better idea?

It's not ugly IMHO. There are more tests for -1 like this, e.g. in
compaction_suitable(). Maybe just add some comment such as:

/*
  * When called via /proc/sys/vm/compact_memory make sure we compact
  * the whole zone regardless of cached scanner positions.
  */

> diff --git a/mm/compaction.c b/mm/compaction.c
> index 8c0d945..5b4e255 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -1587,6 +1587,9 @@ static void __compact_pgdat(pg_data_t *pgdat, struct compact_control *cc)
>                   INIT_LIST_HEAD(&cc->freepages);
>                   INIT_LIST_HEAD(&cc->migratepages);
>
> +               if (cc->order == -1)
> +                       __reset_isolation_suitable(zone);
> +
>                   if (cc->order == -1 || !compaction_deferred(zone, cc->order))
>                           compact_zone(zone, cc);
>
>
>

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

WARNING: multiple messages have this Message-ID (diff)
From: Vlastimil Babka <vbabka@suse.cz>
To: Gioh Kim <gioh.kim@lge.com>,
	akpm@linux-foundation.org, rientjes@google.com,
	iamjoonsoo.kim@lge.com, mgorman@suse.de
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, gunho.lee@lge.com
Subject: Re: [PATCH] [RFC] mm/compaction: initialize compaction information
Date: Fri, 20 Mar 2015 08:51:31 +0100	[thread overview]
Message-ID: <550BD183.5020005@suse.cz> (raw)
In-Reply-To: <550B5CD1.5010306@lge.com>

On 03/20/2015 12:33 AM, Gioh Kim wrote:
>>> diff --git a/mm/compaction.c b/mm/compaction.c
>>> index 8c0d945..827ec06 100644
>>> --- a/mm/compaction.c
>>> +++ b/mm/compaction.c
>>> @@ -1587,8 +1587,10 @@ static void __compact_pgdat(pg_data_t *pgdat, struct compact_control *cc)
>>>                    INIT_LIST_HEAD(&cc->freepages);
>>>                    INIT_LIST_HEAD(&cc->migratepages);
>>>
>>> -               if (cc->order == -1 || !compaction_deferred(zone, cc->order))
>>> +               if (cc->order == -1 || !compaction_deferred(zone, cc->order)) {
>>> +                       __reset_isolation_suitable(zone);
>>
>> This will also trigger reset when called from kswapd through compact_pgdat() and
>> !compaction_deferred() is true.
>> The reset should be restricted to cc->order == -1 which only happens from /proc
>> trigger.
>>
>>>                            compact_zone(zone, cc);
>>> +               }
>>>
>>>                    if (cc->order > 0) {
>>>                            if (zone_watermark_ok(zone, cc->order,
>>>
>>
>>
>
> I've not been familiar with compaction code.
> I think cc->order is -1 only if __compact_pgdat is called via /proc.

Yes that's what I meant.

> This is ugly but I don't have better solution.
> Do you have better idea?

It's not ugly IMHO. There are more tests for -1 like this, e.g. in
compaction_suitable(). Maybe just add some comment such as:

/*
  * When called via /proc/sys/vm/compact_memory make sure we compact
  * the whole zone regardless of cached scanner positions.
  */

> diff --git a/mm/compaction.c b/mm/compaction.c
> index 8c0d945..5b4e255 100644
> --- a/mm/compaction.c
> +++ b/mm/compaction.c
> @@ -1587,6 +1587,9 @@ static void __compact_pgdat(pg_data_t *pgdat, struct compact_control *cc)
>                   INIT_LIST_HEAD(&cc->freepages);
>                   INIT_LIST_HEAD(&cc->migratepages);
>
> +               if (cc->order == -1)
> +                       __reset_isolation_suitable(zone);
> +
>                   if (cc->order == -1 || !compaction_deferred(zone, cc->order))
>                           compact_zone(zone, cc);
>
>
>


  reply	other threads:[~2015-03-20  7:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  5:30 [PATCH] [RFC] mm/compaction: initialize compaction information Gioh Kim
2015-03-19  5:30 ` Gioh Kim
2015-03-19  8:41 ` Vlastimil Babka
2015-03-19  8:41   ` Vlastimil Babka
2015-03-19  8:52   ` Gioh Kim
2015-03-19  8:52     ` Gioh Kim
2015-03-19  9:01     ` Vlastimil Babka
2015-03-19  9:01       ` Vlastimil Babka
2015-03-19 23:33       ` Gioh Kim
2015-03-19 23:33         ` Gioh Kim
2015-03-20  7:51         ` Vlastimil Babka [this message]
2015-03-20  7:51           ` Vlastimil Babka
2015-03-20 13:00         ` [PATCH][RFCv2] mm/compaction: reset compaction scanner positions Gioh Kim
2015-03-20 13:00           ` Gioh Kim
2015-03-20 13:49           ` Vlastimil Babka
2015-03-20 13:49             ` Vlastimil Babka
2015-03-21 11:53             ` Gioh Kim
2015-03-21 11:53               ` Gioh Kim

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=550BD183.5020005@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=gioh.kim@lge.com \
    --cc=gunho.lee@lge.com \
    --cc=iamjoonsoo.kim@lge.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.