On So, 12.11.17 20:17, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
> > And then there's also the big issue: the cgroup code is complex enough
> > given that we need to support three different setups. I'd really
> > prefer if we'd not add even more to that. In fact, I am really looking
> > fo
On Fri, Nov 10, 2017 at 12:16 PM, Lennart Poettering
wrote:
> On Fr, 10.11.17 11:11, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
>
>> On Wed, Nov 8, 2017 at 9:25 PM, Lennart Poettering
>> wrote:
>> > On Sa, 28.10.17 22:01, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
>> >
>> >> Hello,
On Fr, 10.11.17 11:11, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
> On Wed, Nov 8, 2017 at 9:25 PM, Lennart Poettering
> wrote:
> > On Sa, 28.10.17 22:01, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
> >
> >> Hello,
> >>
> >> I am trying to have cpu controller on v1 and memory control
On Wed, Nov 8, 2017 at 9:25 PM, Lennart Poettering
wrote:
> On Sa, 28.10.17 22:01, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
>
>> Hello,
>>
>> I am trying to have cpu controller on v1 and memory controller on
>> unified but it is not working the way I am expecting. When I enable
>> CONFIG_
On Sa, 28.10.17 22:01, Umut Tezduyar Lindskog (u...@tezduyar.com) wrote:
> Hello,
>
> I am trying to have cpu controller on v1 and memory controller on
> unified but it is not working the way I am expecting. When I enable
> CONFIG_MEMCG, cgroup is popping up in /proc/cgroups and
> mount_cgroup_co
Hello,
I am trying to have cpu controller on v1 and memory controller on
unified but it is not working the way I am expecting. When I enable
CONFIG_MEMCG, cgroup is popping up in /proc/cgroups and
mount_cgroup_controllers() is mounting it very early. Once it is
mounted in v1, it becomes unavailabl