From: Minchan Kim <minchan.kim@gmail.com>
To: Iram Shahzad <iram.shahzad@jp.fujitsu.com>
Cc: Wu Fengguang <fengguang.wu@intel.com>, Mel Gorman <mel@csn.ul.ie>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: compaction: trying to understand the code
Date: Tue, 24 Aug 2010 15:52:37 +0900 [thread overview]
Message-ID: <AANLkTikTu3jx5WyYEDZY2mk99V+w7kxL5k7xJDS+QZ+m@mail.gmail.com> (raw)
In-Reply-To: <8E31CE28A1354C43BBAD0BDEFA10494E@rainbow>
On Tue, Aug 24, 2010 at 2:07 PM, Iram Shahzad
<iram.shahzad@jp.fujitsu.com> wrote:
>> One question is, why kswapd won't proceed after isolating all the pages?
>> If it has done with the isolated pages, we'll see growing inactive_anon
>> numbers.
>>
>> /proc/vmstat should give more clues on any possible page reclaim
>> activities. Iram, would you help post it?
>
> I am not sure which point of time are you interested in, so I am
> attaching /proc/vmstat log of 3 points.
>
> too_many_isolated_vmstat_before_frag.txt
> This one is taken before I ran my test app which attempts
> to make fragmentation
> too_many_isolated_vmstat_before_compaction.txt
> This one is taken after running the test app and before
> running compaction.
> too_many_isolated_vmstat_during_compaction.txt
> This one is taken a few minutes after running compaction.
> To take this I ran compaction in background.
>
> Thanks
> Iram
>
Hmm.. Never happens reclaim. Strange.
In addtion, pgpgin is always 4.
pgpgin 4
pgpgout 0
Is it possible?
What kinds of filesystem do you use?
Do you boot from NFS?
Do your system have any non-mainline(ie, doesn't merged into linux
kernel tree) driver, file system or any feature?
Maybe your config file can answer this questions.
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-08-24 6:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 11:08 Iram Shahzad
2010-08-17 11:10 ` Mel Gorman
2010-08-18 8:19 ` Iram Shahzad
2010-08-18 15:41 ` Wu Fengguang
2010-08-19 7:09 ` Iram Shahzad
2010-08-19 7:45 ` Wu Fengguang
2010-08-19 7:46 ` Mel Gorman
2010-08-19 8:08 ` Wu Fengguang
2010-08-19 8:15 ` Mel Gorman
2010-08-19 8:29 ` Wu Fengguang
2010-08-20 5:45 ` Iram Shahzad
2010-08-20 5:50 ` Wu Fengguang
2010-08-20 6:13 ` Iram Shahzad
2010-08-19 16:00 ` Minchan Kim
2010-08-20 5:31 ` Iram Shahzad
2010-08-20 5:34 ` Wu Fengguang
2010-08-20 9:35 ` Mel Gorman
2010-08-20 10:22 ` Minchan Kim
2010-08-22 15:31 ` Minchan Kim
2010-08-22 23:23 ` Wu Fengguang
2010-08-23 1:58 ` Minchan Kim
2010-08-23 3:03 ` Iram Shahzad
2010-08-23 9:10 ` Minchan Kim
2010-08-26 8:51 ` Mel Gorman
2010-08-23 7:18 ` Mel Gorman
2010-08-23 17:14 ` Minchan Kim
2010-08-24 0:27 ` Wu Fengguang
2010-08-24 5:07 ` Iram Shahzad
2010-08-24 6:52 ` Minchan Kim [this message]
2010-08-26 8:05 ` Iram Shahzad
2010-08-23 7:16 ` Mel Gorman
2010-08-23 9:07 ` Minchan Kim
2010-08-20 10:23 ` Wu Fengguang
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=AANLkTikTu3jx5WyYEDZY2mk99V+w7kxL5k7xJDS+QZ+m@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=iram.shahzad@jp.fujitsu.com \
--cc=kosaki.motohiro@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