On Fri, Jul 10, 2009 at 02:01:48PM +0200, Ivana Varekova wrote:
> Hello,
> I'm planing to do some tools to go through system of mounted 
> controllers, created cgroups and parameters of cgroups and so on so I 
> propose this system of tools:
> Feedback welcomed.
> 
> Ivana Hutarova Varekova
> -----------------------
> List groups and controllers:
> 
> lscgroup:
> list mounted/unounted controllers/ cgroups/ cgroup parameters:
> 
> Syntax
> lscgroup [-m] [-a] [controller1] [controller2] [...]
> lscgroup -s [-t] [<list of controllers>[:group]]
> lscgroup -p [-r name] <list of controllers:group>
> 
> Descryption:
> lscgroup without -s display mounted controllers:
> -m .. shows mount pouints too
> -a .. shouws unmounted controllers too
> if controller is on input then
> 
> 
> lscgroup with -s option list all cgroups

>From the discussion we had on IRC, I thought this option was meant for
it to list the subsystems available on the system (not just mounted). I
think we should look to split the tools as per the functionality and
then try to group them as opposed to trying to do it all in one place.

> in all controllers, in given controller, in given cgroup of given controller
> -t .. will display it in "tree" structure
> 
> lscgroup with -p option list the parameters and values in a group
>  -r name - show specified value only
> 
> 
> Examples:
> $ lscgroup
> cpuset,cpu
> devices
> 

I am not sure I agree with this. lscgroup in my mind means, list
cgroups. So it should be similar to ls and lists all the cgroups (maybe
at the same level as the cgroup to which the shell belongs, unless you
give an argument?)

> $ lscgroup -m
> cpuset,cpu /mnt/cgroup/cpu
> devices /mnt/cgroup/devices
> 
> $ lscgroup -ma
> cpuset,cpu /mnt/cgroup/cpu
> devices /mnt/cgroup/devices
> cpuacct
> ns
> memory
> freezer
> 
> $ lscgroup -m cpu
> cpuset,cpu /mnt/cgroup/cpu
> 

These make sense.

> $ lscgroup -s

This one I don't agree with

> cpu,cpuset:/
> cpu,cpuset:/first
> cpu,cpuset:/first/subgroup
> cpu,cpuset:/second
> devices:/
> devices:/alpha
> devices:/beta
> 
> $ lscgroup -s -t
> cpu,cpuset:
>  + first
>  | + subgroup
>  + second
> 
> devices:
>  + alpha
>  + beta
> 
> $ lscgroup -s cpu
> cpu,cpuset:/
> cpu,cpuset:/first
> cpu,cpuset:/first/subgroup
> cpu,cpuset:/second
> 
> $ lscgroup -s cpu:first
> first/subgroup
> 
> $ lscgroup -p cpu:first

What about making is lscgroup -l (similar to ls -l) which will list all
details? (Or am I being totally insane here :))

> cpu.rt_period_us 1000000
> cpu.rt_runtime_us 0
> cpuset.cpu_exclusive 0
> cpuset.cpus 0-1
> cpuset.mem_exclusive 0
> cpuset.mem_hardwall 0
> cpuset.memory_migrate 0
> cpuset.memory_pressure 0
> cpuset.memory_spread_page 0
> cpuset.memory_spread_slab 0
> cpuset.mems 0
> cpuset.sched_load_balance 1
> cpuset.sched_relax_domain_level -1
> cpu.shares 1024
> 
> 
> $ lscgroup -p -r cpuset.cpus -r cpuset.mems cpu:first

OK, now we are reaching the stage of tooo many options :)

> 0-1
> 1

thanks,
-- 
regards,
Dhaval

------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Libcg-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/libcg-devel

Reply via email to