Currently, Android dalvik VM leverages cpu cgroup to determine whether to use kernel scheduler policies, /dev/cpuctl is mounted in init.rc by default. You can create a sub-cpu cgroup under /dev/cpuctl, and control the priorization of processes there as long as your process is granted with CAP_SYS_NICE capability or running as root.
Ken On Mon, May 28, 2012 at 6:55 AM, Kanishka Ariyapala <kanishka...@gmail.com>wrote: > after some googling came to know that android framework is it self using > cgroups. Is it the reason for the device or resource busy error? > Dose it mean that I won't be able to use cgroups? > > > On Mon, May 28, 2012 at 12:26 AM, DK <kanishka...@gmail.com> wrote: > >> Hi, >> >> I have trouble configuring cgroups, please help! When I issue the >> following command I get the error "mount: Device or resource busy" >> >> # mount -t cgroup -ocpu none /dev/cpuctl >> >> These are the configurations options that I have enabled. >> >> CONFIG_GROUP_SCHED=y >> CONFIG_FAIR_GROUP_SCHED=y >> CONFIG_RT_GROUP_SCHED=y >> # CONFIG_USER_SCHED is not set >> CONFIG_CGROUP_SCHED=y >> CONFIG_CGROUPS=y >> CONFIG_CGROUP_DEBUG=y >> CONFIG_CGROUP_NS=y >> CONFIG_CGROUP_FREEZER=y >> CONFIG_CGROUP_DEVICE=y >> CONFIG_CGROUP_CPUACCT=y >> CONFIG_RESOURCE_COUNTERS=y >> CONFIG_CGROUP_MEM_RES_CTLR=y >> CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y >> CONFIG_MM_OWNER=y >> >> Why is mount saying device busy? >> >> note: I was following the steps in the documentation(sched-design- >> CFS.txt) >> >> Regards, >> Kanishka >> >> -- >> unsubscribe: android-kernel+unsubscr...@googlegroups.com >> website: http://groups.google.com/group/android-kernel > > > -- > unsubscribe: android-kernel+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-kernel > -- -- Ken Chen -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
