[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1154976236.19249.9.camel@localhost.localdomain>
Date: Mon, 07 Aug 2006 11:43:56 -0700
From: Dave Hansen <haveblue@...ibm.com>
To: rohitseth@...gle.com
Cc: Kirill Korotaev <dev@...ru>, "Martin J. Bligh" <mbligh@...igh.org>,
vatsa@...ibm.com, Alan Cox <alan@...rguk.ukuu.org.uk>,
Andrew Morton <akpm@...l.org>, mingo@...e.hu,
nickpiggin@...oo.com.au, sam@...ain.net,
linux-kernel@...r.kernel.org, dev@...nvz.org, efault@....de,
balbir@...ibm.com, sekharan@...ibm.com, nagar@...son.ibm.com,
pj@....com, Andrey Savochkin <saw@...ru>
Subject: Re: [RFC, PATCH 0/5] Going forward with Resource Management - A
cpu controller
On Mon, 2006-08-07 at 11:31 -0700, Rohit Seth wrote:
> I think it is not a problem for OpenVZ because there is not that much
> of
> sharing going between containers as you mentioned (btw, this least
> amount of sharing is a very good thing). Though I'm not sure if one
> has
> to go to the extent of doing fractions with memory accounting. If the
> containers are set up in such a way that there is some sharing across
> containers then it is okay to be unfair and charge one of those
> containers for the specific resource completely.
Right, and if you do reclaim against containers which are over their
limits, the containers being unfairly charged will tend to get hit
first. But, once this happens, I would hope that the ownership of those
shared pages should settle out among all of the users.
If you have 100 containers sharing 100 pages, container0 might be
charged for all 100 pages at first, but I'd hope that eventually
containers 0->99 would each get charged for a single page.
-- Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists