From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: balbir@linux.vnet.ibm.com,
Evgeniy Ivanov <lolkaantimat@gmail.com>,
linux-mm@kvack.org,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
gthelen@google.com
Subject: Re: Question about cgroup hierarchy and reducing memory limit
Date: Tue, 30 Nov 2010 10:23:49 +0900 [thread overview]
Message-ID: <20101130102349.5bb5e671.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20101130090333.0c8c1728.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, 30 Nov 2010 09:03:33 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > Oh! oh! I'd hate to do this in the fault path
> >
> Why ? We have per-cpu stock now and infulence of this is minimum.
> We never hit this.
> If problem, I'll use per-cpu value but it seems to be overkill.
I'll remove all atomic ops.
BTW, if you don't like waitqueue, what is alternative ?
Keeping memory cgroup limit broken as returning -EBUSY is better ?
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-11-30 1:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 16:59 Evgeniy Ivanov
2010-11-24 0:47 ` KAMEZAWA Hiroyuki
2010-11-24 12:17 ` Evgeniy Ivanov
2010-11-25 1:04 ` KAMEZAWA Hiroyuki
2010-11-25 10:51 ` Evgeniy Ivanov
2010-11-29 6:58 ` KAMEZAWA Hiroyuki
2010-11-29 14:02 ` Balbir Singh
2010-11-30 0:03 ` KAMEZAWA Hiroyuki
2010-11-30 1:23 ` 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=20101130102349.5bb5e671.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=gthelen@google.com \
--cc=linux-mm@kvack.org \
--cc=lolkaantimat@gmail.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