From: Round Robinjp <roundrobinjp@yahoo.co.jp>
To: mel@csn.ul.ie
Cc: linux-mm@kvack.org, iram.shahzad@jp.fujitsu.com
Subject: Re: compaction: why depends on HUGETLB_PAGE
Date: Sat, 31 Jul 2010 01:44:09 +0900 (JST) [thread overview]
Message-ID: <20100730164414.88965.qmail@web4208.mail.ogk.yahoo.co.jp> (raw)
> > Please could you elaborate a little more why depending on
> > compaction to satisfy other high-order allocation is not good.
> >
>
> At the very least, it's not a situation that has been tested heavily and
> because other high-order allocations are typically not movable. In the
> worst case, if they are both frequent and long-lived they *may* eventually
> encounter fragmentation-related problems. This uncertainity is why it's
> not good. It gets worse if there is no swap as eventually all movable pages
> will be compacted as much as possible but there still might not be enough
> contiguous memory for a high-order page because other pages are pinned.
I am interested in this topic too.
How about using compaction for infrequent short-lived
high-order allocations? Is there any problem in that case?
(apart from the point that it is not tested for that purpose)
Also how about using compaction as a preparation
for partial refresh?
RR
--------------------------------------
Get the new Internet Explorer 8 optimized for Yahoo! JAPAN
http://pr.mail.yahoo.co.jp/ie8/
--
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 reply other threads:[~2010-07-30 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 16:44 Round Robinjp [this message]
2010-07-30 16:49 ` Mel Gorman
-- strict thread matches above, loose matches on Subject: below --
2010-07-29 1:53 Iram Shahzad
2010-07-29 12:57 ` Mel Gorman
2010-07-30 2:56 ` Iram Shahzad
2010-07-30 9:57 ` 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=20100730164414.88965.qmail@web4208.mail.ogk.yahoo.co.jp \
--to=roundrobinjp@yahoo.co.jp \
--cc=iram.shahzad@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