linux-kernel - Re: [ckrm-tech] [PATCH 4/7] UBC: syscalls (user interface)

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] [day] [month] [year] [list]

Message-ID: <44EAC5CA.8020605@sw.ru>
Date:	Tue, 22 Aug 2006 12:52:26 +0400
From:	Kirill Korotaev <dev@...ru>
To:	Paul Jackson <pj@....com>
CC:	riel@...hat.com, Linux@...-sf-spam2-b.sourceforge.net,
	ckrm-tech@...ts.sourceforge.net, haveblue@...ibm.com,
	linux-kernel@...r.kernel.org, ak@...e.de, hch@...radead.org,
	saw@...ru, alan@...rguk.ukuu.org.uk, rohitseth@...gle.com,
	hugh@...itas.com, Christoph@...-sf-spam2-b.sourceforge.net,
	mingo@...e.hu, devel@...nvz.org, xemul@...nvz.org
Subject: Re: [ckrm-tech] [PATCH 4/7] UBC: syscalls (user interface)

Paul Jackson wrote:
>>this doesn't allow memory overcommitment, does it?
> 
> 
> Uh - no - I don't think so.  You can over commit
> the memory of a task in a small cpuset just as well
> as you can a task in a big cpuset or even one in the
> top cpuset covering the entire system.
> 
> Perhaps I didn't understand your point.
My point was that when you have lots of containers
their summary memory limit can be much higher then available RAM.
This allows bursts of memory usage for containers, since
it is very unlikely for all of them to consume the memory
simulatenously. E.g. hosters usually oversell memory
say 2 times on the node.

So the question was whether it is possbile to overcommit memory
with NUMA emulation?

Thanks,
Kirill

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