linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Patrick.Le-Dot@bull.net (Patrick.Le-Dot)
To: alan@lxorguk.ukuu.org.uk
Cc: balbir@in.ibm.com, ckrm-tech@lists.sourceforge.net,
	dev@openvz.org, haveblue@us.ibm.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	rohitseth@google.com
Subject: Re: [ckrm-tech] [RFC][PATCH 5/8] RSS controller task migration support
Date: Fri, 17 Nov 2006 15:42:06 +0100 (CET)	[thread overview]
Message-ID: <20061117144206.3013D1B6A2@openx4.frec.bull.fr> (raw)

On Fri, 17 Nov 2006 14:05:13 +0000
> ...
> There are two reasons for wanting memory guarantees
> 
> #1      To be sure a user can't toast the entire box but just their own
>         compartment (eg web hosting)

Well, this seems not a situation to add a guarantee to this user
but a limit...

> ...
> #2      To ensure all apps continue to make progress

or to ensure that a job is ready to work without to have to pay the
cost of a lot of pagination in...


>> If the limit is a "hard limit" then we have implemented reservation and
>> this is too strict.
>
> Thats fundamentally a judgement based on your particular workload and
> constraints.
Nop.
You can read this on the wiki page...

I'm just saying that the implementation of guarantee with limits seems to
be not enough for #2.

> If I am web hosting then I don't generally care if my end
> users compartment blows up under excess load, I care that the other 200
> customers using the box don't suffer and all phone me to complain.

I agree : limit is necessary and should be a "hard limit" (even if the
controler needs an internal threeshold like a "soft limit" to decide to
wakeup the kswapd).
But this is not the topic (not yet:-)

Patrick

--
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-11-17 14:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-17 14:42 Patrick.Le-Dot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-17 13:25 Patrick.Le-Dot
2006-11-17 14:05 ` Alan
2006-11-17 16:34 ` Balbir Singh
2006-11-15 11:59 Patrick.Le-Dot
2006-11-15 16:37 ` [ckrm-tech] " 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=20061117144206.3013D1B6A2@openx4.frec.bull.fr \
    --to=patrick.le-dot@bull.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=balbir@in.ibm.com \
    --cc=ckrm-tech@lists.sourceforge.net \
    --cc=dev@openvz.org \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rohitseth@google.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