Re: [systemd-devel] [PATCH] cgroup: After MemmoryAccounting=yes running scope has no memusage

2014-04-09 Thread Stef Walter
On 09.04.2014 23:45, Lennart Poettering wrote: > On Tue, 08.04.14 12:11, Stef Walter (s...@thewalter.net) wrote: > >> Setting the 'MemoryAccounting' unit property to true, puts the >> unit into the right cgroup but does the memory.usage_in_bytes >> does not reflect the pages already allocated to t

Re: [systemd-devel] [PATCH] cgroup: After MemmoryAccounting=yes running scope has no memusage

2014-04-09 Thread Lennart Poettering
On Tue, 08.04.14 12:11, Stef Walter (s...@thewalter.net) wrote: > Setting the 'MemoryAccounting' unit property to true, puts the > unit into the right cgroup but does the memory.usage_in_bytes > does not reflect the pages already allocated to the processes > in that cgroup. > > This is because th

Re: [systemd-devel] [PATCH] cgroup: After MemmoryAccounting=yes running scope has no memusage

2014-04-08 Thread David Timothy Strauss
+1 from me. Seems like a good bugfix. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

[systemd-devel] [PATCH] cgroup: After MemmoryAccounting=yes running scope has no memusage

2014-04-08 Thread Stef Walter
Setting the 'MemoryAccounting' unit property to true, puts the unit into the right cgroup but does the memory.usage_in_bytes does not reflect the pages already allocated to the processes in that cgroup. This is because the memory.move_charge_at_immigrate needs to be set before migrating processes