From: kamezawa.hiroyu@jp.fujitsu.com
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
balbir@linux.vnet.ibm.com, hugh@veritas.com, linux-mm@kvack.org,
menage@google.com, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Re: memo: mem+swap controller
Date: Fri, 1 Aug 2008 01:31:41 +0900 (JST) [thread overview]
Message-ID: <4668997.1217521901885.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20080731220323.61e44dec.nishimura@mxp.nes.nec.co.jp>
>> > > Following is state transition and counter handling design memo.
>> > > This uses "3" counters to handle above conrrectly. If you have other lo
gic,
>> > > please teach me. (and blame me if my diagram is broken.)
>> > >
>> > I don't think counting "disk swap" is good idea(global linux
>> > dosen't count it).
>> > Instead, I prefer counting "total swap"(that is swap entry).
>> >
>> Maybe my illustration is bad.
>>
>> total_swap = swap_cache + disk_swap. Yes, I count swp_entry.
>> But just divides it to on-memory or not.
>>
>> This is just a state transition problem. When we counting only total_swap,
>> we cannot avoid double counting of a swap_cache as memory and as swap.
>>
>I agree.
>My intention was not counting only total_swap, but counting both
>total_swap and swap_cache.
>
At early stage of diaglam, I just added total_swap counter.
(total_swap here means # of used swp_entry.)
And failed to write diaglam ;( Maybe selection of counters was bad.
If just 2 counters are enough, it's better.
Hmm..
- on_memory .... # of pages used
- disk_swap .... # of swp_entry without SwapCache
limit_in_bytes ... limits on_memory
total_limit ... limits on_mempry + disk_swap.
can work ?
I'd like to write a sample patch in the next week.
Thanks,
-Kame
--
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:[~2008-07-31 16:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 1:15 KAMEZAWA Hiroyuki
2008-07-31 6:18 ` KOSAKI Motohiro
2008-07-31 6:25 ` Daisuke Nishimura
2008-07-31 6:51 ` KAMEZAWA Hiroyuki
2008-07-31 13:03 ` Daisuke Nishimura
2008-07-31 16:31 ` kamezawa.hiroyu [this message]
2008-08-01 3:05 ` Daisuke Nishimura
2008-08-01 3:28 ` Balbir Singh
2008-08-01 4:02 ` Daisuke Nishimura
2008-08-01 4:13 ` Balbir Singh
2008-08-01 4:57 ` Daisuke Nishimura
2008-08-01 5:07 ` memcg swappiness (Re: memo: mem+swap controller) YAMAMOTO Takashi
2008-08-01 5:25 ` Balbir Singh
2008-08-01 6:37 ` YAMAMOTO Takashi
2008-08-01 6:46 ` Balbir Singh
2008-09-09 9:17 ` YAMAMOTO Takashi
2008-09-09 14:07 ` Balbir Singh
2008-08-01 3:20 ` memo: mem+swap controller Balbir Singh
2008-08-01 3:45 ` KAMEZAWA Hiroyuki
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=4668997.1217521901885.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
/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