From: Minchan Kim <minchan@kernel.org>
To: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Hugh Dickins <hughd@google.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
Dave Jones <davej@redhat.com>, Cong Wang <amwang@redhat.com>,
Markus Trippelsdorf <markus@trippelsdorf.de>,
Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v10] mm: compaction: handle incorrect MIGRATE_UNMOVABLE type pageblocks
Date: Mon, 11 Jun 2012 10:26:49 +0900 [thread overview]
Message-ID: <4FD54959.6060500@kernel.org> (raw)
In-Reply-To: <201206081046.32382.b.zolnierkie@samsung.com>
Hi Bartlomiej,
On 06/08/2012 05:46 PM, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> This version is much simpler as it just uses __count_immobile_pages()
> instead of using its own open coded version and it integrates changes
That's a good idea. I don't have noticed that function is there.
When I look at the function, it has a problem, too.
Please, look at this.
https://lkml.org/lkml/2012/6/10/180
If reviewer is okay that patch, I would like to resend your patch based on that.
> from Minchan Kim (without page_count change as it doesn't seem correct
Why do you think so?
If it isn't correct, how can you prevent racing with THP page freeing?
> and __count_immobile_pages() does the check in the standard way; if it
> still is a problem I think that removing 1st phase check altogether
> would be better instead of adding more locking complexity).
>
> The patch also adds compact_rescued_unmovable_blocks vmevent to vmstats
> to make it possible to easily check if the code is working in practice.
I think that part should be another patch.
1. Adding new vmstat would be arguable so it might interrupt this patch merging.
2. New vmstat adding is just for this patch is effective or not in real practice
so if we prove it in future, let's revert the vmstat. Separating it would make it
easily.
--
Kind regards,
Minchan Kim
--
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>
next prev parent reply other threads:[~2012-06-11 1:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 8:46 Bartlomiej Zolnierkiewicz
2012-06-08 21:18 ` Andrew Morton
2012-06-11 2:05 ` Minchan Kim
2012-06-11 10:37 ` Bartlomiej Zolnierkiewicz
2012-06-11 1:26 ` Minchan Kim [this message]
2012-06-11 10:43 ` Bartlomiej Zolnierkiewicz
2012-06-11 13:39 ` Minchan Kim
2012-06-11 14:54 ` Bartlomiej Zolnierkiewicz
2012-06-11 23:37 ` Minchan 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=4FD54959.6060500@kernel.org \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=amwang@redhat.com \
--cc=b.zolnierkie@samsung.com \
--cc=davej@redhat.com \
--cc=hughd@google.com \
--cc=kosaki.motohiro@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=markus@trippelsdorf.de \
--cc=mgorman@suse.de \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.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