linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: yamamoto@valinux.co.jp (YAMAMOTO Takashi)
To: nishimura@mxp.nes.nec.co.jp
Cc: minoura@valinux.co.jp, linux-mm@kvack.org,
	containers@lists.osdl.org, hugh@veritas.com,
	balbir@linux.vnet.ibm.com
Subject: Re: [RFC][PATCH] another swap controller for cgroup
Date: Tue, 25 Mar 2008 17:57:23 +0900 (JST)	[thread overview]
Message-ID: <20080325085723.698C11E936D@siro.lan> (raw)
In-Reply-To: Your message of "Tue, 25 Mar 2008 13:35:53 +0900" <47E88129.1010705@mxp.nes.nec.co.jp>

> YAMAMOTO Takashi wrote:
> > hi,
> > 
> >> 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?
> > 
> > my patch tends to yield more swap cache because it makes try_to_unmap
> > fail and shrink_page_list leaves swap cache in that case.
> > i'm not sure how it causes 1GB swap cache, tho.
> > 
> 
> Agree.
> 
> I suspected that the cause of this problem was the behavior
> of shrink_page_list as you said, so I thought one of Rik's
> split-lru patchset:
> 
>   http://lkml.org/lkml/2008/3/4/492
>   [patch 04/20] free swap space on swap-in/activation
> 
> would reduce the usage of swap cache to half of the total swap.
> But it didn't help, so I think there may be some other causes.

do you mean you tested with the patch in the url?
i don't think remove_exclusive_swap_page works for us
because our page has more references than it expects.
ie. ptes, cache, isolate_page

(unless your tree has another change for remove_exclusive_swap_page.
i haven't checked other patches in the patchset.)

YAMAMOTO Takashi

> 
> 
> 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  8:57 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
2008-03-25  3:10     ` YAMAMOTO Takashi
2008-03-25  4:35       ` Daisuke Nishimura
2008-03-25  8:57         ` YAMAMOTO Takashi [this message]
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=20080325085723.698C11E936D@siro.lan \
    --to=yamamoto@valinux.co.jp \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=minoura@valinux.co.jp \
    --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