Re: [RFC] libcg: design and plans

Paul Menage wrote:
On Wed, Mar 5, 2008 at 3:07 AM, Dhaval Giani <dhaval@xxxxxxxxxxxxxxxxxx> wrote:
OK. Hmm, I've not really thought about it. At first thought, it should
not be very difficult. Only thing I am not sure is the arbitrary
grouping of the groups (ok, a bit confusing).

I suspect that the main form of composite grouping is going to be
between parents and children. E.g. you might want to say things like:

create_group(A, memory=1G, cpu=100)
create_group(B, parent=A, memory=inherit, cpu=20)
create_group(C, parent=A, memory=inherit, cpu=30)

i.e. both B and C inherit/share their memory limit from their parent,
but have their own CPU groups (child groups of their parent?)


No, we don't plan on doing that. What we plan on doing is

1. Specify the mount point for each controller
2. In the create group API, specify the name of the group and the various
parameters.

If for example CPU is mounted at /cpu and Memory at /mem

Then a specification for creation of group A would be of the form

create_group(A, cpu=100, memory=100M)

Then,

/cpu/A has shares set to 100 and /mem/A has memory.limit set to 100M

If you want to create subgroups under A, you specify

create_group(A/B, memory=200M, cpu=50)

That would create /cpu/A/B and /mem/A/B

Please note that memory and CPU hierarchy needs work in the kernel. The shares
and hierarchy support is pending. We need to make the res_counters
infrastructure aware of hierarchies.



--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: Hawkins ideas on building AIs
    ... >> built a computer system with a very fast memory, ... >> to specify the basic operations to occur in the different levels. ... I was talking about a hierarchy where you ... comparison-projection algorithm works in more detail? ...
    (sci.cognitive)
  • Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector
    ... (the CPU cgroup controller provides hierarchy control for the full hierarchy). ... whereas memory works in terms of absolute memory size. ...
    (Linux-Kernel)
  • Re: [mm] [PATCH 4/4] Memory cgroup hierarchy feature selector
    ... (the CPU cgroup controller provides hierarchy control for the full hierarchy). ... whereas memory works in terms of absolute memory size. ...
    (Linux-Kernel)
  • Re: [rfc][patch] sched: remove smpnice
    ... to an idle CPU should be a "good thing" unless the time taken for the move is longer than the time that will pass before the task becomes the running task on its current CPU. ... The less of the cache-memory hierarchy the two CPUs share, ... the penalty to the task for memory accesses after the move. ... A task moved to a far away CPU will be cache cold for ...
    (Linux-Kernel)
  • Re: [rfc][patch] sched: remove smpnice
    ... running task on its current CPU. ... The less of the cache-memory hierarchy the two CPUs share, ... the penalty to the task for memory accesses after the move. ... two hyperthreads on the same core share essentially all ...
    (Linux-Kernel)
Loading