On May 31, 10:47 am, Ken Chen <
ken.chen....@gmail.com> wrote:
> On Wed, May 30, 2012 at 3:56 AM, Kanishka Ariyapala
> <
kanishka...@gmail.com>wrote:
>
> > Thank you Ken for the reply. I created a cgroup under /dev/cpuctl and
> > added a process to the tasks file. using echo PID > tasks. however it wont
> > get registered there, of course the PID changes every time when the
> > application is re-started. In my case I was testing with browser and the
> > music player. Once you exit and come back the PID is gone.
>
> > <Ken>That's expected behavior of cgroup.
>
> Since NAME of the app is constant(ex - com.android.browser) I will have to> get the PID from the task_struct I guess, and assign the PID. How ever what
> > is the mechanism to make a process change between two cgroups? In a
> > programmatical manner with out issuing echo PID. (can it be hard coded in
> > the source..)
>
> > <Ken> Simply echo PID to new cgroup, it will be moved out from the
>
> previous one automatically.
>
> > I don't know if this is a stupid Q anyways, normal applications have the
> > user name as something like app_XX is there any way of changing that to a
> > root? through capabilities may be?
> > CAP_SYS_NICE is defined in capability.h how do I know if it is granted to
> > my process? if not granting it. (in the kernel space as well as inside the
> > app)
>
> <Ken> You can not changing app_xx to root, but root can grant CAP_SYS_NICE
> to app_xx.
>
> <DK> How can this be done? in the kernel source or in side the application
>
>
>
> > On Tue, May 29, 2012 at 4:17 PM, Ken Chen <
ken.chen....@gmail.com> wrote:
>
> >> 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?
>