From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: YAMAMOTO Takashi <yamamoto@valinux.co.jp>
Cc: balbir@linux.vnet.ibm.com, linux-mm@kvack.org,
containers@lists.osdl.org, xemul@openvz.org
Subject: Re: [PATCH][RFC] memory.min_usage again
Date: Mon, 29 Sep 2008 11:55:13 +0900 [thread overview]
Message-ID: <20080929115513.5db72cfd.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20080929004332.13B0083F2@siro.lan>
On Mon, 29 Sep 2008 09:43:32 +0900 (JST)
yamamoto@valinux.co.jp (YAMAMOTO Takashi) wrote:
> > >
> > > I would prefer to see some heuristics around such a feature, mostly around the
> > > priority that do_try_to_free_pages() to determine how desperate we are for
> > > reclaiming memory.
> > >
> > Taking "priority" of memory reclaim path into account is good.
> >
> > ==
> > static unsigned long shrink_inactive_list(unsigned long max_scan,
> > struct zone *zone, struct scan_control *sc,
> > int priority, int file)
> > ==
> > How about ignore min_usage if "priority < DEF_PRIORITY - 2" ?
>
> are you suggesting ignoring mlock etc as well in that case?
>
No. Just freeing pages, which are usually freed is good.
==
int mem_cgroup_canreclaim(struct page *page, struct mem_cgroup *mem1,
int priority)
{
struct page_cgroup *pc;
int result = 1;
if (mem1 != NULL)
return 1;
/* global lru is busy ? */
if (priority < DEF_PEIORITY - 1)
return 1;
....
}
==
Maybe min_usage can works as *soft* mlock by this.
Or another idea.
Making memory.min_usage as memory.reclaim_priority_level and allows
priority_level == 0 => can_reclaim() returns 1 always.
priority_level == 1 => can_reclaim returns 1 if priority < DEF_PRIORITY-1.
priority_level == 2 => can_reclaim returns 1 if priority < DEF_PRIORITY-2.
(and only 0,1,2 are allowed.)
setting min_usage will not be prefered by lru management people.
This can work as "advice" to global lru.
Hmm ?
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>
prev parent reply other threads:[~2008-09-29 2:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071204040934.44AF41D0BA3@siro.lan>
2008-09-10 8:44 ` YAMAMOTO Takashi
2008-09-10 8:53 ` KOSAKI Motohiro
2008-09-10 15:32 ` Balbir Singh
2008-09-12 9:46 ` KAMEZAWA Hiroyuki
2008-09-29 0:43 ` YAMAMOTO Takashi
2008-09-29 2:21 ` Balbir Singh
2008-09-29 2:55 ` KAMEZAWA Hiroyuki [this message]
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=20080929115513.5db72cfd.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=linux-mm@kvack.org \
--cc=xemul@openvz.org \
--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