On Tue, 29 Nov 2011 22:40:58 +0100Jarry <mr.jarry@gmail.com> wrote:
> On 29-Nov-11 21:40, Herbert Poetzl wrote:
>
> >> And what is even worse, it seems there are actually
> >> no limits at all. vserver-stat show that vs-guest
> >> takes more memory than I allowed. But the "old way"
> >> (rss.soft, rss.hard) at least works. Strange...
> >
> > I'm pretty sure it doesn't work with kernels newer than
> > 2.6.34 though, because the code doing that simply isn't
> > there anymore :)
>
> I see I mixed it a "little bit". I'm running 2 kernels:
>
> 1). 2.6.35 with vs2.3.0.36.32, where memory limits
> using cgroups do not work. I have no idea why...
works for me with 2.6.35.14-vs2.3.0.36.33.
see attached screen log showing configuration and demonstrating memory limits.
i can also verify that the same configuration works for 3.1.4-vs2.3.2.1 and
3.0.12-vs2.3.2.1 (minus the memory.memsw.limit_in_bytes because i didn't
notice i had to set CONFIG_CGROUP_MEM_RES_CTLR_SWAP_ENABLED though
CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y as in 2.6.35).
corey
-- undefined@pobox.com > 2). 2.6.22 with vs2.2.0.7, where memory limits > using rss.hard and rss.soft do work. Only with > this kernel I see correct limited memory in vs-guest. > > There is one more vserver-patch in my repository (2.3.1 > maybe for kernel 3.x?), but it is masked as "unstable". > I'm not sure it is suitable for server, but I'll try it. > > Jarry > -- > _______________________________________________________________ > This mailbox accepts e-mails only from selected mailing-lists! > Everything else is considered to be spam and therefore deleted. >