From: Dave Hansen <dave@linux.vnet.ibm.com>
To: balbir@linux.vnet.ibm.com
Cc: Paul Menage <menage@google.com>,
Dave Hansen <haveblue@us.ibm.com>,
Andrea Righi <righi.andrea@gmail.com>,
Hugh Dickins <hugh@veritas.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [discuss] memrlimit - potential applications that can use
Date: Tue, 19 Aug 2008 08:58:44 -0700 [thread overview]
Message-ID: <1219161525.23641.125.camel@nimitz> (raw)
In-Reply-To: <48AA73B5.7010302@linux.vnet.ibm.com>
On Tue, 2008-08-19 at 12:48 +0530, Balbir Singh wrote:
> 1. To provide a soft landing mechanism for applications that exceed their memory
> limit. Currently in the memory resource controller, we swap and on failure OOM.
> 2. To provide a mechanism similar to memory overcommit for control groups.
> Overcommit has finer accounting, we just account for virtual address space usage.
> 3. Vserver will directly be able to port over on top of memrlimit (their address
> space limitation feature)
Balbir,
This all seems like a little bit too much hand waving to me. I don't
really see a single concrete user in the "potential applications" here.
I really don't understand why you're pushing this so hard if you don't
have anyone to actually use it.
I just don't see anyone that *needs* it. There's a lot of "it would be
nice", but no "needs".
-- Dave
--
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-08-19 15:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 7:18 Balbir Singh
2008-08-19 15:58 ` Dave Hansen [this message]
2008-08-19 16:45 ` Balbir Singh
2008-08-19 17:41 ` Dave Hansen
2008-08-20 8:26 ` Balbir Singh
2008-08-20 16:29 ` Dave Hansen
2008-08-21 3:25 ` Balbir Singh
2008-08-21 7:43 ` KAMEZAWA Hiroyuki
2008-08-21 10:26 ` Balbir Singh
2008-08-21 10:59 ` KAMEZAWA Hiroyuki
2008-08-21 11:13 ` Balbir Singh
2008-08-21 15:18 ` righi.andrea
2008-08-20 13:25 ` righi.andrea
2008-08-20 16:38 ` Dave Hansen
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=1219161525.23641.125.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=righi.andrea@gmail.com \
/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