linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Magnus Damm" <magnus.damm@gmail.com>
To: sekharan@us.ibm.com
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
	Magnus Damm <magnus@valinux.co.jp>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org, Valerie Clement <Valerie.Clement@bull.net>
Subject: Re: [PATCH 03/03] Unmapped: Add guarantee code
Date: Sat, 11 Mar 2006 21:29:55 +0900	[thread overview]
Message-ID: <aec7e5c30603110429tcad0ff1lc0073c613486eec5@mail.gmail.com> (raw)
In-Reply-To: <1142005277.8174.107.camel@linuxchandra>

On 3/11/06, Chandra Seetharaman <sekharan@us.ibm.com> wrote:
> On Fri, 2006-03-10 at 15:04 +0900, Magnus Damm wrote:
> > On 3/10/06, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> > > Magnus Damm wrote:
> > > If your app is really that specialised then maybe it can use mlock. If
> > > not, maybe the VM is currently broken.
> > >
> > > You do have a real-world workload that is significantly improved by this,
> > > right?
> >
> > Not really, but I think there is a demand for memory resource control today.
>
> As a person who is working on CKRM, I totally agree with this :)

Hehe, good to head that I'm not alone. =)

> > The memory controller in ckrm also breaks out the LRU, but puts one
> > LRU instance in each class. My code does not depend on ckrm, but it
> > should be possible to have some kind of resource control with this
>
> i do not understand how breaking lru lists into mapped/unmapped pages
> and providing a knob to control the proportion of mapped/unmapped pages
> in a node help in resource control.

It is one type of resource control. It is of course not a complete
solution like ckrm, but on machines with more than one node (or a
regular PC with numa emulation) it is possible to create partitions
using CPUSETS and then use this patch to control the amount of memory
that should be dedicated for say mapped pages on each node.

CKRM and CPUSETS are the ways to provide resource control today.
CPUSETS is coarse-grained, but CKRM aims for finer granularity. None
of them have a way to control the ratio between mapped and unmapped
pages, excluding this patch.

I'd like to see CKRM merged, but I'm not the one calling the shots
(probably fortunate enough for everyone). I think CKRM has the same
properties as the ClockPRO work - it would be nice to have it included
in mainline, but these patches modify lots of crital code and
therefore has problems getting accepted that easily.

So this patch is YASSITRD. (Yet Another Small Step In The Right Direction)

Thank you!

/ magnus

--
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:[~2006-03-11 12:29 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-10  3:44 [PATCH 00/03] Unmapped: Separate unmapped and mapped pages Magnus Damm
2006-03-10  3:44 ` [PATCH 01/03] Unmapped: Implement two LRU:s Magnus Damm
2006-03-10 19:16   ` Christoph Lameter
2006-03-11 12:14     ` Magnus Damm
2006-03-10  3:44 ` [PATCH 02/03] Unmapped: Modify LRU behaviour Magnus Damm
2006-03-10  3:44 ` [PATCH 03/03] Unmapped: Add guarantee code Magnus Damm
2006-03-10  4:57   ` Nick Piggin
2006-03-10  6:04     ` Magnus Damm
2006-03-10 15:41       ` Chandra Seetharaman
2006-03-11 12:29         ` Magnus Damm [this message]
2006-03-15 15:32           ` Chandra Seetharaman
2006-03-10  4:55 ` [PATCH 00/03] Unmapped: Separate unmapped and mapped pages Nick Piggin
2006-03-10  5:55   ` Magnus Damm
2006-03-10  7:52 ` Arjan van de Ven
2006-03-10 13:19   ` Magnus Damm
2006-03-10 14:05     ` Arjan van de Ven
2006-03-11 11:52       ` Magnus Damm
2006-03-11 20:58     ` Peter Zijlstra
2006-03-13  2:28       ` Magnus Damm
2006-03-10 12:22 ` Peter Zijlstra
2006-03-10 13:38   ` Magnus Damm
2006-03-11 21:08     ` Peter Zijlstra
2006-03-13  3:05       ` Magnus Damm
2006-03-10 19:12 ` Christoph Lameter
2006-03-11 11:56   ` Magnus Damm

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=aec7e5c30603110429tcad0ff1lc0073c613486eec5@mail.gmail.com \
    --to=magnus.damm@gmail.com \
    --cc=Valerie.Clement@bull.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=magnus@valinux.co.jp \
    --cc=nickpiggin@yahoo.com.au \
    --cc=sekharan@us.ibm.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