From: Minchan Kim <minchan.kim@gmail.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: akpm@linux-foundation.org, Mel Gorman <mel@csn.ul.ie>,
arthur.marsh@internode.on.net, cladisch@googlemail.com,
hannes@cmpxchg.org, kamezawa.hiroyu@jp.fujitsu.com,
linux-mm <linux-mm@kvack.org>
Subject: Re: + mm-compaction-use-async-migration-for-__gfp_no_kswapd-and-enforce-no-writeback.patch added to -mm tree
Date: Thu, 24 Mar 2011 17:54:00 +0900 [thread overview]
Message-ID: <AANLkTim0Xa+ydGhNqt3hYxaX81Jo9KyvvwdvtDamy1Np@mail.gmail.com> (raw)
In-Reply-To: <20110323143632.GL5698@random.random>
On Wed, Mar 23, 2011 at 11:36 PM, Andrea Arcangeli <aarcange@redhat.com> wrote:
> On Wed, Mar 23, 2011 at 03:01:33PM +0900, Minchan Kim wrote:
>> Okay. I will look at result.
>> If the problem happens again with reverted patch of page_alloc.c,
>> Don't we have to investigate further the problem happens with SLUB or
>> some driver's big memory allocation which is lower than 2M? We didn't
>> see the problem allocation under 2M but async migration's history was
>> short so we can't make sure it.
>
> Yes, probably. This is also why I hope the page_alloc.c part didn't
> make a difference. We kept it to be sure to make any sign of sync
> migration to go away from the stack traces, but I hope it's not so
> important anymore now. Reclaim eventually also becomes synchronous.
>
>> Don't you want to add async migration for low order allocation like SLUB?
>> If you don't want to do async migration low order allocation, we can
>> add the check if (gfp_flags & __GFP_RETRY) && (order >= 9 or some
>> threshold) for async migration?
>>
>> My point is to avoid implicit hidden meaning of __GFP_NO_KSWAPD
>> although __GFP_REPEAT already does it.
>
> I see your point, so let's think about it after testing of the
> reversal of the page_alloc.c change. If that's not necessary we just
> reverse it and it already solves these concerns.
Absolutely.
>
>> If async migration is going on and meet the dirty page, the patch can
>> return the -EBUSY so the page could put back to head of LRU but the
>> old migration can be going on although the page is dirty.
>
> Ok, but in term of LRU it's not like we're going to help much in
> skipping the page in compaction, it'd leave the sync pages there, and
> only list_del the async pages. I think it's mostly a cpu saving
> optimization, I doubt the lru ordering will be much more accurate by
> not doing list_del on the sync pages considering we would list_del
> the rest but not the sync part.
Yes. In terms of all LRU pages, I doubt it but isn't it better than
current meaningless rotation if we can do it easily?
Anyway, It's not a urgent issue so I don't mind it. :)
Thanks.
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-03-24 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201103222153.p2MLrD0x029642@imap1.linux-foundation.org>
2011-03-22 22:58 ` Minchan Kim
2011-03-23 0:25 ` Andrea Arcangeli
2011-03-23 6:01 ` Minchan Kim
2011-03-23 14:36 ` Andrea Arcangeli
2011-03-24 8:54 ` Minchan Kim [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=AANLkTim0Xa+ydGhNqt3hYxaX81Jo9KyvvwdvtDamy1Np@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arthur.marsh@internode.on.net \
--cc=cladisch@googlemail.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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