From: Minchan Kim <minchan@kernel.org>
To: Rik van Riel <riel@redhat.com>, hannes@cmpxchg.org
Cc: Alexey Ivanov <rbtz@yandex-team.ru>,
"gnehzuil.lzheng@gmail.com" <gnehzuil.lzheng@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
yinghan@google.com
Subject: Re: mapped pagecache pages vs unmapped pages
Date: Tue, 10 Apr 2012 10:25:08 +0900 [thread overview]
Message-ID: <4F838BF4.7020104@kernel.org> (raw)
In-Reply-To: <4F838390.1080909@redhat.com>
2012-04-10 i??i ? 9:49, Rik van Riel i?' e,?:
> On 04/09/2012 08:31 PM, Minchan Kim wrote:
>> 2012-04-10 i??i ? 8:50, Alexey Ivanov i?' e,?:
>>
>>> Did you consider making this ratio tunable, at least manually(i.e.
>>> via sysctl)?
>>> I suppose we are not the only ones with almost-whole-ram-mmaped
>>> workload.
>>
>> Personally, I think it's not good approach.
>> It depends on kernel's internal implemenatation which would be changed
>> in future as we chagend it at 2.6.28.
>
> I also believe that a tunable for this is not going to be
> a very workable approach, for the simple reason that changing
> the value does not make a predictable change in the effectiveness
> of working set detection or protection.
>
>> In my opinion, kernel just should do best effort to keep active working
>> set except some critical pages which are code pages.
>
> Johannes has some experimental code to measure refaults, and
> calculate their distance in a multi-zone, multi-cgroup environment.
>
> That would allow us to predictably place things in the working set
> as required.
>
Hannes, it can help many people if you post your code. ;)
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: Rik van Riel <riel@redhat.com>, hannes@cmpxchg.org
Cc: Alexey Ivanov <rbtz@yandex-team.ru>,
"gnehzuil.lzheng@gmail.com" <gnehzuil.lzheng@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
yinghan@google.com
Subject: Re: mapped pagecache pages vs unmapped pages
Date: Tue, 10 Apr 2012 10:25:08 +0900 [thread overview]
Message-ID: <4F838BF4.7020104@kernel.org> (raw)
In-Reply-To: <4F838390.1080909@redhat.com>
2012-04-10 오전 9:49, Rik van Riel 쓴 글:
> On 04/09/2012 08:31 PM, Minchan Kim wrote:
>> 2012-04-10 오전 8:50, Alexey Ivanov 쓴 글:
>>
>>> Did you consider making this ratio tunable, at least manually(i.e.
>>> via sysctl)?
>>> I suppose we are not the only ones with almost-whole-ram-mmaped
>>> workload.
>>
>> Personally, I think it's not good approach.
>> It depends on kernel's internal implemenatation which would be changed
>> in future as we chagend it at 2.6.28.
>
> I also believe that a tunable for this is not going to be
> a very workable approach, for the simple reason that changing
> the value does not make a predictable change in the effectiveness
> of working set detection or protection.
>
>> In my opinion, kernel just should do best effort to keep active working
>> set except some critical pages which are code pages.
>
> Johannes has some experimental code to measure refaults, and
> calculate their distance in a multi-zone, multi-cgroup environment.
>
> That would allow us to predictably place things in the working set
> as required.
>
Hannes, it can help many people if you post your code. ;)
--
Kind regards,
Minchan Kim
next prev parent reply other threads:[~2012-04-10 1:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 0:29 mapped pagecache pages vs unmapped pages Alexey Ivanov
2012-04-06 7:16 ` gnehzuil.lzheng
2012-04-06 7:16 ` gnehzuil.lzheng
2012-04-09 17:11 ` Alexey Ivanov
2012-04-09 17:11 ` Alexey Ivanov
2012-04-09 18:14 ` Rik van Riel
2012-04-09 18:14 ` Rik van Riel
2012-04-09 23:50 ` Alexey Ivanov
2012-04-09 23:50 ` Alexey Ivanov
2012-04-10 0:31 ` Minchan Kim
2012-04-10 0:31 ` Minchan Kim
2012-04-10 0:49 ` Rik van Riel
2012-04-10 0:49 ` Rik van Riel
2012-04-10 1:25 ` Minchan Kim [this message]
2012-04-10 1:25 ` Minchan Kim
2012-04-09 18:17 ` Ying Han
2012-04-09 18:17 ` Ying Han
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=4F838BF4.7020104@kernel.org \
--to=minchan@kernel.org \
--cc=gnehzuil.lzheng@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rbtz@yandex-team.ru \
--cc=riel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.