From: Pavel Emelyanov <xemul@openvz.org>
To: balbir@linux.vnet.ibm.com
Cc: linux-mm@kvack.org, Hugh Dickins <hugh@veritas.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
Paul Menage <menage@google.com>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
"Eric W. Biederman" <ebiederm@xmission.com>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Rik Van Riel <riel@redhat.com>,
Herbert Poetzl <herbert@13thfloor.at>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [RFC] [PATCH 1/4] Modify resource counters to add soft limit support
Date: Wed, 13 Feb 2008 20:38:47 +0300 [thread overview]
Message-ID: <47B32B27.4090406@openvz.org> (raw)
In-Reply-To: <47B326BA.7040000@linux.vnet.ibm.com>
Balbir Singh wrote:
> Pavel Emelyanov wrote:
>> Balbir Singh wrote:
>
>> Resource counter accounts for arbitrary resource. Memory pressure
>> and memory reclamation both only make sense in case we're dealing
>> with memory controller. Please, remove this comment or move it to
>> memcontrol.c.
>>
>
> Yes, they always have. The concept of soft limits, hard limits, guarantees
> applies to all resources. Why do you say they apply only to memory controller? I
I said that *memory pressure and memory reclamation*, not the soft limits
in general, applies to memory controller only :)
> can change the comment to make the definition generic for all resources.
>
>
--
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-02-13 17:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 15:12 [RFC] [PATCH 0/4] Add soft limits to the memory controller Balbir Singh
2008-02-13 15:12 ` [RFC] [PATCH 1/4] Modify resource counters to add soft limit support Balbir Singh
2008-02-13 17:12 ` Pavel Emelyanov
2008-02-13 17:19 ` Balbir Singh
2008-02-13 17:38 ` Pavel Emelyanov [this message]
2008-02-13 17:54 ` Balbir Singh
2008-02-13 15:12 ` [RFC] [PATCH 2/4] Add the soft limit interface Balbir Singh
2008-02-13 15:12 ` [RFC] [PATCH 3/4] Reclaim from groups over their soft limit under memory pressure Balbir Singh
2008-02-14 7:30 ` KAMEZAWA Hiroyuki
2008-02-14 7:40 ` Balbir Singh
2008-02-14 8:42 ` KAMEZAWA Hiroyuki
2008-02-14 9:16 ` Balbir Singh
2008-02-15 4:17 ` Paul Menage
2008-02-15 4:25 ` Balbir Singh
2008-02-15 5:07 ` KAMEZAWA Hiroyuki
2008-02-15 5:16 ` Paul Menage
2008-02-15 5:18 ` Balbir Singh
2008-02-15 5:30 ` Paul Menage
2008-02-15 5:33 ` KAMEZAWA Hiroyuki
2008-02-15 5:29 ` KAMEZAWA Hiroyuki
2008-02-15 6:36 ` Balbir Singh
2008-02-14 10:27 ` YAMAMOTO Takashi
2008-02-15 3:19 ` Balbir Singh
2008-02-13 15:12 ` [RFC] [PATCH 4/4] Add soft limit documentation Balbir Singh
2008-02-13 15:59 ` Randy Dunlap
2008-02-13 16:08 ` Balbir Singh
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=47B32B27.4090406@openvz.org \
--to=xemul@openvz.org \
--cc=Lee.Schermerhorn@hp.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=ebiederm@xmission.com \
--cc=herbert@13thfloor.at \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=nickpiggin@yahoo.com.au \
--cc=riel@redhat.com \
--cc=rientjes@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.