From: Minchan Kim <minchan.kim@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Ying Han <yinghan@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Venkatesh Pallipadi <venki@google.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH] vmscan: prevent background aging of anon page in no swap system
Date: Tue, 31 Aug 2010 12:46:53 +0900 [thread overview]
Message-ID: <AANLkTik=6kRdz0LJnRRhddW_Lp8osis-4Y7EGc4u5x0z@mail.gmail.com> (raw)
In-Reply-To: <4C7C6959.3030801@redhat.com>
On Tue, Aug 31, 2010 at 11:30 AM, Rik van Riel <riel@redhat.com> wrote:
> On 08/30/2010 09:23 PM, Minchan Kim wrote:
>
>> Ying's one and mine both has a same effect.
>> Only difference happens swap is full. My version maintains old
>> behavior but Ying's one changes the behavior. I admit swap full is
>> rare event but I hoped not changed old behavior if we doesn't find any
>> problem.
>> If kswapd does aging when swap full happens, is it a problem?
>
> It may be a good thing, since swap will often be freed again
> (when something is swapped in, or exits).
>
> Having some more anonymous pages sit on the inactive list
> gives them a chance to get used again, potentially giving
> us a better chance of preserving the working set when swap
> is full or near full a lot of the time.
Do you mean we would be better to do background aging when swap is full?
I wanted it. So I used total_swap_pages to protect working set when
swap is full.
But Ying and KOSAKI's don't like it since it makes code inconsistent
or not simply.
And I agree it's rare event as KOSAKI mentioned.
Hmm... What do you think about it?
If you don't mind, I will resend latest version(use nr_swap_page usage
and compile out inactive_anon_is_low in case of !CONFIG_SWAP).
--
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-31 3:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-29 15:43 Minchan Kim
2010-08-29 15:49 ` Rik van Riel
2010-08-29 17:45 ` Ying Han
2010-08-29 20:03 ` Rik van Riel
2010-08-29 20:56 ` Ying Han
2010-08-29 21:23 ` Ying Han
2010-08-29 22:26 ` Rik van Riel
2010-08-30 0:18 ` Minchan Kim
2010-08-30 5:40 ` Ying Han
2010-08-30 6:16 ` Minchan Kim
2010-08-31 0:56 ` KOSAKI Motohiro
2010-08-31 1:10 ` Minchan Kim
2010-08-31 1:18 ` KOSAKI Motohiro
2010-08-31 1:36 ` Minchan Kim
2010-08-31 1:41 ` KOSAKI Motohiro
2010-08-31 0:56 ` KOSAKI Motohiro
2010-08-31 1:23 ` Minchan Kim
2010-08-31 1:38 ` KOSAKI Motohiro
2010-08-31 2:02 ` Minchan Kim
2010-08-31 2:09 ` KOSAKI Motohiro
2010-08-31 3:47 ` Minchan Kim
2010-08-31 2:30 ` Rik van Riel
2010-08-31 3:46 ` Minchan Kim [this message]
2010-09-03 21:06 ` Andrew Morton
2010-09-03 21:23 ` Rik van Riel
2010-09-03 21:45 ` Ying Han
2010-09-03 21:47 ` Ying Han
2010-09-03 21:56 ` Andrew Morton
2010-09-04 1:12 ` Venkatesh Pallipadi
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='AANLkTik=6kRdz0LJnRRhddW_Lp8osis-4Y7EGc4u5x0z@mail.gmail.com' \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=venki@google.com \
--cc=yinghan@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox