Hello, the reproducer is really tricky, and I thing cgred restart should be necessary in this case. Ivana
----- Original Message ----- > From: "Libo Chen" <clbchenlibo.c...@huawei.com> > To: "Libcg Development list" <libcg-devel@lists.sourceforge.net> > Cc: "Ivana Hutarova Varekova" <varek...@redhat.com>, "Wengmeiling" > <wengmeiling.w...@huawei.com>, "Huang Qiang" > <h.huangqi...@huawei.com>, "Li Zefan" <lize...@huawei.com> > Sent: Wednesday, October 23, 2013 8:15:41 AM > Subject: Question about the dull cgred > > Hi guys, > > Cgred cannot obtain the controller change in the Cgroup once the service > has started. > > example: > > cgrules.conf : > root:ping cpu test1 > % memory test2 > > > cgconfig.conf: > mount { > cpu = /cgroup/cpu; > } > > group test1{ > cpu { > } > } > > > #/etc/init.d/cgconfig start > #/etc/init.d/cgred start > #ping a.b.c.d > > the ping is in test1. > > #ctrl+c > #mount -t cgroup -o memory cgroup /cgroup/memory > #cgcreate -g memory:test2 > #ping a.b.c.d > > but the ping cannot be attached to test2. Looking through the code, the > reason is > in cgroup_attach_task_pid(), cg_mount_table initialized by cgroup_init > doesn't conclude > memory controller. > > I know restart cgred is ok, but it is not enough smart. I think the most > ideal way is > cgred can apperceive the controller change, and then update > cg_mount_table. > > What is your opinion? > > > > > > > > ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ Libcg-devel mailing list Libcg-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libcg-devel