From: Mel Gorman <mel@csn.ul.ie>
To: Rik van Riel <riel@redhat.com>
Cc: linux-mm@kvack.org, lkml <linux-kernel@vger.kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan.kim@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>
Subject: Re: [PATCH v2 -mm 3/3] mm: only defer compaction for failed order and higher
Date: Wed, 25 Jan 2012 16:21:13 +0000 [thread overview]
Message-ID: <20120125162112.GF3901@csn.ul.ie> (raw)
In-Reply-To: <4F2025D9.9050409@redhat.com>
On Wed, Jan 25, 2012 at 10:55:05AM -0500, Rik van Riel wrote:
> On 01/25/2012 10:41 AM, Mel Gorman wrote:
>
> >>--- a/mm/compaction.c
> >>+++ b/mm/compaction.c
> >>@@ -673,9 +673,18 @@ static int __compact_pgdat(pg_data_t *pgdat, struct compact_control *cc)
> >> INIT_LIST_HEAD(&cc->freepages);
> >> INIT_LIST_HEAD(&cc->migratepages);
> >>
> >>- if (cc->order< 0 || !compaction_deferred(zone))
> >>+ if (cc->order< 0 || !compaction_deferred(zone, cc->order))
> >> compact_zone(zone, cc);
> >>
> >>+ if (cc->order> 0) {
> >>+ int ok = zone_watermark_ok(zone, cc->order,
> >>+ low_wmark_pages(zone), 0, 0);
> >>+ if (ok&& cc->order> zone->compact_order_failed)
> >>+ zone->compact_order_failed = cc->order + 1;
> >>+ else if (!ok&& cc->sync)
> >>+ defer_compaction(zone, cc->order);
> >>+ }
> >>+
> >
> >That needs a comment. I think what you're trying to do is reset
> >compat_order_failed once compaction is successful.
> >
> >The "!ok&& cc->sync" check may be broken. __compact_pgdat() is
> >called from kswapd, not direct compaction so cc->sync will not be true.
>
> The problem with doing that is that we would be deferring
> synchronous compaction (by allocators), just because
> asynchronous compaction from kswapd failed...
>
I should have been clear. I was not suggesting that we defer compaction
here for !cc->sync. I was pointing out that the code as-is is dead.
> That is the reason the code is like it is above. And
> indeed, it will not defer compaction from this code path
> right now.
>
Ok, that was my understanding, I just wanted to be sure I understood
your intentions.
> Then again, neither does async compaction from page
> allocators defer compaction - only sync compaction does.
>
Yep, this is on purpose.
> If it turns out we need a separate compaction deferral
> for async compaction, we can always introduce that later,
> and this code will be ready for it.
>
Ok, I can accept that.
> If you prefer, I can replace the whole "else if" bit with
> a big fat comment explaining why we cannot currently
> defer compaction from this point.
>
Explaining that it is dead code for kswapd would also do.
If you do replace the code, add a WARN_ON(cc->sync) in case the
assumption changes in the future so defer_compaction() gets thought
about properly.
--
Mel Gorman
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mel@csn.ul.ie>
To: Rik van Riel <riel@redhat.com>
Cc: linux-mm@kvack.org, lkml <linux-kernel@vger.kernel.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Minchan Kim <minchan.kim@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>
Subject: Re: [PATCH v2 -mm 3/3] mm: only defer compaction for failed order and higher
Date: Wed, 25 Jan 2012 16:21:13 +0000 [thread overview]
Message-ID: <20120125162112.GF3901@csn.ul.ie> (raw)
In-Reply-To: <4F2025D9.9050409@redhat.com>
On Wed, Jan 25, 2012 at 10:55:05AM -0500, Rik van Riel wrote:
> On 01/25/2012 10:41 AM, Mel Gorman wrote:
>
> >>--- a/mm/compaction.c
> >>+++ b/mm/compaction.c
> >>@@ -673,9 +673,18 @@ static int __compact_pgdat(pg_data_t *pgdat, struct compact_control *cc)
> >> INIT_LIST_HEAD(&cc->freepages);
> >> INIT_LIST_HEAD(&cc->migratepages);
> >>
> >>- if (cc->order< 0 || !compaction_deferred(zone))
> >>+ if (cc->order< 0 || !compaction_deferred(zone, cc->order))
> >> compact_zone(zone, cc);
> >>
> >>+ if (cc->order> 0) {
> >>+ int ok = zone_watermark_ok(zone, cc->order,
> >>+ low_wmark_pages(zone), 0, 0);
> >>+ if (ok&& cc->order> zone->compact_order_failed)
> >>+ zone->compact_order_failed = cc->order + 1;
> >>+ else if (!ok&& cc->sync)
> >>+ defer_compaction(zone, cc->order);
> >>+ }
> >>+
> >
> >That needs a comment. I think what you're trying to do is reset
> >compat_order_failed once compaction is successful.
> >
> >The "!ok&& cc->sync" check may be broken. __compact_pgdat() is
> >called from kswapd, not direct compaction so cc->sync will not be true.
>
> The problem with doing that is that we would be deferring
> synchronous compaction (by allocators), just because
> asynchronous compaction from kswapd failed...
>
I should have been clear. I was not suggesting that we defer compaction
here for !cc->sync. I was pointing out that the code as-is is dead.
> That is the reason the code is like it is above. And
> indeed, it will not defer compaction from this code path
> right now.
>
Ok, that was my understanding, I just wanted to be sure I understood
your intentions.
> Then again, neither does async compaction from page
> allocators defer compaction - only sync compaction does.
>
Yep, this is on purpose.
> If it turns out we need a separate compaction deferral
> for async compaction, we can always introduce that later,
> and this code will be ready for it.
>
Ok, I can accept that.
> If you prefer, I can replace the whole "else if" bit with
> a big fat comment explaining why we cannot currently
> defer compaction from this point.
>
Explaining that it is dead code for kswapd would also do.
If you do replace the code, add a WARN_ON(cc->sync) in case the
assumption changes in the future so defer_compaction() gets thought
about properly.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2012-01-25 16:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 18:18 [PATCH v2 -mm 0/3] kswapd vs compaction improvements Rik van Riel
2012-01-24 18:18 ` Rik van Riel
2012-01-24 18:21 ` [PATCH v2 -mm 1/3] mm: reclaim at order 0 when compaction is enabled Rik van Riel
2012-01-24 18:21 ` Rik van Riel
2012-01-25 15:00 ` Mel Gorman
2012-01-25 15:00 ` Mel Gorman
2012-01-25 15:27 ` Rik van Riel
2012-01-25 15:27 ` Rik van Riel
2012-01-25 16:07 ` Mel Gorman
2012-01-25 16:07 ` Mel Gorman
2012-01-25 17:17 ` Rik van Riel
2012-01-25 17:17 ` Rik van Riel
2012-01-25 22:16 ` Andrea Arcangeli
2012-01-25 22:16 ` Andrea Arcangeli
2012-01-26 2:12 ` Rik van Riel
2012-01-26 2:12 ` Rik van Riel
2012-01-24 18:22 ` [PATCH v2 -mm 2/3] mm: kswapd carefully call compaction Rik van Riel
2012-01-24 18:22 ` Rik van Riel
2012-01-25 15:19 ` Mel Gorman
2012-01-25 15:19 ` Mel Gorman
2012-01-24 18:23 ` [PATCH v2 -mm 3/3] mm: only defer compaction for failed order and higher Rik van Riel
2012-01-24 18:23 ` Rik van Riel
2012-01-25 15:41 ` Mel Gorman
2012-01-25 15:41 ` Mel Gorman
2012-01-25 15:55 ` Rik van Riel
2012-01-25 15:55 ` Rik van Riel
2012-01-25 16:21 ` Mel Gorman [this message]
2012-01-25 16:21 ` 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=20120125162112.GF3901@csn.ul.ie \
--to=mel@csn.ul.ie \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.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.