linux-kernel - Re: [RFC, PATCH 0/5] Going forward with Resource Management

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 07 Aug 2006 12:46:57 -0700
From:	Martin Bligh <mbligh@...igh.org>
To:	rohitseth@...gle.com
Cc:	Dave Hansen <haveblue@...ibm.com>, Kirill Korotaev <dev@...ru>,
	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

Rohit Seth wrote:
> On Mon, 2006-08-07 at 11:43 -0700, Dave Hansen wrote:
> 
>>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.
>>
> 
> 
> I think there is lot of simplicity and value add by charging one
> container (even unfairly) for one resource completely.  This puts the
> onus on system admin to set up the containers appropriately.

It also saves you from maintaining huge lists against each page.

Worse case, you want to bill everyone who opens that address_space
equally. But the semantics on exit still suck.

What was Alan's quote again? "unfair, unreliable, inefficient ...
pick at least one out of the three". or something like that.

M.
-
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/