linux-kernel - Re: [patch00/05]: Containers(V2)- Introduction

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:	Wed, 20 Sep 2006 16:26:48 -0700
From:	Rohit Seth <rohitseth@...gle.com>
To:	Paul Jackson <pj@....com>
Cc:	clameter@....com, ckrm-tech@...ts.sourceforge.net,
	devel@...nvz.org, npiggin@...e.de, linux-kernel@...r.kernel.org
Subject: Re: [patch00/05]: Containers(V2)- Introduction

On Wed, 2006-09-20 at 15:58 -0700, Paul Jackson wrote:
> Seth wrote:
> > So now we depend on getting memory hot-plug to work for faking up these
> > nodes ...for the memory that is already present in the system. It just
> > does not sound logical.
> 
> It's logical to me.  Part of memory hotplug is adding physial memory,
> which is not an issue here.  Part of it is adding another logical
> memory node (turning on another bit in node_online_map) and fixing up
> any code that thought a systems memory nodes were baked in at boottime.
> Perhaps the hardest part is the memory hot-un-plug, which would become
> more urgently needed with such use of fake numa nodes.  The assumption
> that memory doesn't just up and vanish is non-trivial to remove from
> the kernel.  A useful memory containerization should (IMHO) allow for
> both adding and removing such containers.
> 

Absolutely.  Since these containers are not (hard) partitioning the
memory in any way so it is easy to change the limits (effectively
reducing and increasing the memory limits for tasks belonging to
containers).  As you said, memory hot-un-plug is important and it is
non-trivial amount of work.

-rohit

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