linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: balbir@linux.vnet.ibm.com
Cc: yamamoto@valinux.co.jp, minoura@valinux.co.jp,
	Linux MM <linux-mm@kvack.org>,
	Linux Containers <containers@lists.osdl.org>,
	Hugh Dickins <hugh@veritas.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	"IKEDA, Munehiro" <m-ikeda@ds.jp.nec.com>
Subject: Re: [RFC][PATCH] another swap controller for cgroup
Date: Tue, 25 Mar 2008 15:46:28 +0900	[thread overview]
Message-ID: <47E89FC4.4090105@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <47E79CF0.6040308@linux.vnet.ibm.com>

Balbir Singh wrote:
> Daisuke Nishimura wrote:
>> Daisuke Nishimura wrote:
>>> Hi, Yamamoto-san.
>>>
>>> I'm reviewing and testing your patch now.
>>>
>> In building kernel infinitely(in a cgroup of
>> memory.limit=64M and swap.limit=128M, with swappiness=100),
>> almost all of the swap (1GB) is consumed as swap cache
>> after a day or so.
>> As a result, processes are occasionally OOM-killed even when
>> the swap.usage of the group doesn't exceed the limit.
>>
>> I don't know why the swap cache uses up swap space.
>> I will test whether a similar issue happens without your patch.
>> Do you have any thoughts?
>>
>>
>> BTW, I think that it would be better, in the sence of
>> isolating memory resource, if there is a framework
>> to limit the usage of swap cache.
> 
> We had this earlier, but dropped it later due to issues related to swap
> readahead and assigning the pages to the correct cgroup.
> 
Yes, I know.

In my swap subsystem posted before, I charge swap entries
and remember to which cgroup each swap entries is charged
in an array of pointers. So swap caches is charged as swap
not memory, and swap usage including swap cache can be accounted.

There may be better solution, and one of the issue of
my implementation is swap_cgroup_chage() returns error
before reclaiming swap entries which are only used
by swap caches.
I'm considering this issue now.


Thanks,
Daisuke Nishimura.

--
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>

  reply	other threads:[~2008-03-25  6:46 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17  2:04 YAMAMOTO Takashi
2008-03-17  5:11 ` Balbir Singh
2008-03-17  8:15 ` Daisuke Nishimura
2008-03-17  8:50   ` YAMAMOTO Takashi
2008-04-29 22:50     ` YAMAMOTO Takashi
2008-04-30  4:09       ` Daisuke Nishimura
2008-05-22  4:46         ` YAMAMOTO Takashi
2008-05-22  4:54           ` Daisuke Nishimura
2008-05-05  6:11       ` Balbir Singh
2008-05-07  5:50         ` YAMAMOTO Takashi
2008-05-08 15:43           ` Balbir Singh
2008-05-14  3:21             ` YAMAMOTO Takashi
2008-05-14  3:27               ` Paul Menage
2008-05-14  8:44               ` Paul Menage
2008-05-15  6:23                 ` YAMAMOTO Takashi
2008-05-15  7:19                   ` Paul Menage
2008-05-15  8:56                     ` YAMAMOTO Takashi
2008-05-15 12:01                       ` Daisuke Nishimura
2008-05-19  4:14                         ` YAMAMOTO Takashi
2008-03-24 12:10   ` Daisuke Nishimura
2008-03-24 12:22     ` Balbir Singh
2008-03-25  6:46       ` Daisuke Nishimura [this message]
2008-03-25  3:10     ` YAMAMOTO Takashi
2008-03-25  4:35       ` Daisuke Nishimura
2008-03-25  8:57         ` YAMAMOTO Takashi
2008-03-25 12:35           ` Daisuke Nishimura
2008-03-27  6:28             ` YAMAMOTO Takashi
2008-03-28  9:00               ` Daisuke Nishimura
     [not found]                 ` <47ECB3B1.6040500-YQH0OdQVrdy45+QrQBaojngSJqDPrsil@public.gmane.org>
2008-04-08  3:29                   ` YAMAMOTO Takashi
2008-04-10  7:40               ` YAMAMOTO Takashi

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=47E89FC4.4090105@mxp.nes.nec.co.jp \
    --to=nishimura@mxp.nes.nec.co.jp \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=hugh@veritas.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=m-ikeda@ds.jp.nec.com \
    --cc=minoura@valinux.co.jp \
    --cc=yamamoto@valinux.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