From: Patrick.Le-Dot@bull.net (Patrick.Le-Dot)
To: balbir@in.ibm.com
Cc: 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: [RFC][PATCH 5/8] RSS controller task migration support
Date: Tue, 21 Nov 2006 11:01:50 +0100 (CET) [thread overview]
Message-ID: <20061121100150.9ECCF1B6AC@openx4.frec.bull.fr> (raw)
On Fri, 17 Nov 2006 22:04:08 +0530
> ...
> I am not against guarantees, but
>
> Consider the following scenario, let's say we implement guarantees
>
> 1. If we account for kernel resources, how do you provide guarantees
> when you have non-reclaimable resources?
First, the current patch is based only on pages available in the
struct mm.
I doubt that these pages are "non-reclaimable"...
And guarantee should be ignored just because some kernel resources
are marked "non-reclaimable" ?
> 2. If a customer runs a system with swap turned off (which is quite
> common),
quite common, really ?
> then anonymous memory becomes irreclaimable. If a group
> takes more than it's fair share (exceeds its guarantee), you
> have scenario similar to 1 above.
That seems to be just a subset of the "guarantee+limit" model : if
guarantee is not useful for you, don't use it.
I'm not saying that guarantee should be a magic piece of code working
for everybody.
But we have to propose something for the customers who ask for a
guarantee (ie using a system with swap turned on like me and this is
quite common:-)
Patrick
+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ Patrick Le Dot
mailto: P@trick.Le-Dot@bull.net Centre UNIX de BULL SAS
Phone : +33 4 76 29 73 20 1, Rue de Provence BP 208
Fax : +33 4 76 29 76 00 38130 ECHIROLLES Cedex FRANCE
Bull, Architect of an Open World TM
www.bull.com
--
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 reply other threads:[~2006-11-21 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 10:01 Patrick.Le-Dot [this message]
2006-11-21 11:06 ` Balbir Singh
-- strict thread matches above, loose matches on Subject: below --
2006-11-15 11:59 Patrick.Le-Dot
2006-11-09 19:35 [RFC][PATCH 0/8] RSS controller for containers Balbir Singh
2006-11-09 19:36 ` [RFC][PATCH 5/8] RSS controller task migration support 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=20061121100150.9ECCF1B6AC@openx4.frec.bull.fr \
--to=patrick.le-dot@bull.net \
--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