Home » Mailing lists » Devel » [RFC] cgroup basic comounting
| [RFC] cgroup basic comounting [message #44592] |
Fri, 16 December 2011 12:29  |
Glauber Costa
Messages: 916
Registered: October 2011
|
Senior Member |
|
|
Turns out that most of the infrastructure we need to put two controllers in the
same hierarchy is by far already into place. All we need to do is not failing
when we specify two of them.
With this, we can effectively guarantee that by comounting cpu and cpuacct,
we'll have the same set of tasks, therefore allowing us to use cpu cgroup data
to fill in the usage fields in cpuacct.
I decided not to stabilish any dependency between cgroups as Li previously did:
cgroups may or may not be comounted, and any of them can be combined (I don't
see a reason to prevent any combination).
After testing and some trials, I could verify that the current mount behavior
plays well under the plans, so I didn't change it. That is:
* If subsystems A and B aren't mounted, we can comount them.
* If subsystem A is mounted, but B is not:
* we can comount them if A has no children,
* we fail otherwise
* If subsystems A and B are comounted at a location, we can't
mount any of them separately at another point. We do can mount
them together.
* If subsystems A and B are comounted at a location,
* we can comount a third subsystem C, if they have no children
* we fail otherwise
Paul,
Please let me know if this is tuned with the idea you had in mind.
If this is okay, I patch that extracts usage from cpu cgroup data
in case of comount would follow.
Signed-off-by: Glauber Costa <glommer@parallels.com>
CC: Paul Turner <pjt@google.com>
CC: Li Zefan <lizf@cn.fujitsu.com>
---
kernel/cgroup.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/cgroup.c b/kernel/cgroup.c
index 1fd7867..e894a4f 100644
--- a/kernel/cgroup.c
+++ b/kernel/cgroup.c
@@ -1211,9 +1211,9 @@ static int parse_cgroupfs_options(char *data, struct cgroup_sb_opts *opts)
set_bit(i, &opts->subsys_bits);
one_ss = true;
- break;
+ continue;
}
- if (i == CGROUP_SUBSYS_COUNT)
+ if (opts->subsys_bits == 0)
return -ENOENT;
}
--
1.7.6.4
|
|
|
|
|
|
| Re: [RFC] cgroup basic comounting [message #44638 is a reply to message #44592] |
Mon, 19 December 2011 08:00  |
Glauber Costa
Messages: 916
Registered: October 2011
|
Senior Member |
|
|
On 12/19/2011 11:58 AM, Li Zefan wrote:
> Glauber Costa wrote:
>> Turns out that most of the infrastructure we need to put two controllers in the
>> same hierarchy is by far already into place. All we need to do is not failing
>> when we specify two of them.
>>
>
> You don't need to change anything to mount with 2 cgroup subsystems:
>
> # mount -t cgroup -o cpu,cpuacct xxx /mnt
>
> But you may want to revise and make use of the subsys->bind() callback, which
> is called at mount/remount/umount when we attach/remove a controller to/from
> a hierarchy. It's the place you can check if two controllers are going to
> be comounted/seperated.
>
>> With this, we can effectively guarantee that by comounting cpu and cpuacct,
>> we'll have the same set of tasks, therefore allowing us to use cpu cgroup data
>> to fill in the usage fields in cpuacct.
Yeah, that patch was bogus, sorry for the noise.
What I should really have posted is the test code, but I guess I'll go
over that one as well one more time, and then post it.
Thanks
>> I decided not to stabilish any dependency between cgroups as Li previously did:
>> cgroups may or may not be comounted, and any of them can be combined (I don't
>> see a reason to prevent any combination).
>>
>> After testing and some trials, I could verify that the current mount behavior
>> plays well under the plans, so I didn't change it. That is:
>>
>> * If subsystems A and B aren't mounted, we can comount them.
>> * If subsystem A is mounted, but B is not:
>> * we can comount them if A has no children,
>> * we fail otherwise
>> * If subsystems A and B are comounted at a location, we can't
>> mount any of them separately at another point. We do can mount
>> them together.
>> * If subsystems A and B are comounted at a location,
>> * we can comount a third subsystem C, if they have no children
>> * we fail otherwise
>>
>> Paul,
>>
>> Please let me know if this is tuned with the idea you had in mind.
>> If this is okay, I patch that extracts usage from cpu cgroup data
>> in case of comount would follow.
>>
>> Signed-off-by: Glauber Costa<glommer@parallels.com>
>> CC: Paul Turner<pjt@google.com>
>> CC: Li Zefan<lizf@cn.fujitsu.com>
>> ---
>> kernel/cgroup.c | 4 ++--
>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/kernel/cgroup.c b/kernel/cgroup.c
>> index 1fd7867..e894a4f 100644
>> --- a/kernel/cgroup.c
>> +++ b/kernel/cgroup.c
>> @@ -1211,9 +1211,9 @@ static int parse_cgroupfs_options(char *data, struct cgroup_sb_opts *opts)
>> set_bit(i,&opts->subsys_bits);
>> one_ss = true;
>>
>> - break;
>> + continue;
>> }
>> - if (i == CGROUP_SUBSYS_COUNT)
>> + if (opts->subsys_bits == 0)
>> return -ENOENT;
>> }
>>
> --
> To unsubscribe from this list: send the line "unsubscribe cgroups" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
|
|
|
|
| Re: [RFC] cgroup basic comounting [message #44645 is a reply to message #44592] |
Mon, 19 December 2011 07:58 |
Li Zefan
Messages: 90
Registered: February 2008
|
Member |
|
|
Glauber Costa wrote:
> Turns out that most of the infrastructure we need to put two controllers in the
> same hierarchy is by far already into place. All we need to do is not failing
> when we specify two of them.
>
You don't need to change anything to mount with 2 cgroup subsystems:
# mount -t cgroup -o cpu,cpuacct xxx /mnt
But you may want to revise and make use of the subsys->bind() callback, which
is called at mount/remount/umount when we attach/remove a controller to/from
a hierarchy. It's the place you can check if two controllers are going to
be comounted/seperated.
> With this, we can effectively guarantee that by comounting cpu and cpuacct,
> we'll have the same set of tasks, therefore allowing us to use cpu cgroup data
> to fill in the usage fields in cpuacct.
>
> I decided not to stabilish any dependency between cgroups as Li previously did:
> cgroups may or may not be comounted, and any of them can be combined (I don't
> see a reason to prevent any combination).
>
> After testing and some trials, I could verify that the current mount behavior
> plays well under the plans, so I didn't change it. That is:
>
> * If subsystems A and B aren't mounted, we can comount them.
> * If subsystem A is mounted, but B is not:
> * we can comount them if A has no children,
> * we fail otherwise
> * If subsystems A and B are comounted at a location, we can't
> mount any of them separately at another point. We do can mount
> them together.
> * If subsystems A and B are comounted at a location,
> * we can comount a third subsystem C, if they have no children
> * we fail otherwise
>
> Paul,
>
> Please let me know if this is tuned with the idea you had in mind.
> If this is okay, I patch that extracts usage from cpu cgroup data
> in case of comount would follow.
>
> Signed-off-by: Glauber Costa <glommer@parallels.com>
> CC: Paul Turner <pjt@google.com>
> CC: Li Zefan <lizf@cn.fujitsu.com>
> ---
> kernel/cgroup.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/cgroup.c b/kernel/cgroup.c
> index 1fd7867..e894a4f 100644
> --- a/kernel/cgroup.c
> +++ b/kernel/cgroup.c
> @@ -1211,9 +1211,9 @@ static int parse_cgroupfs_options(char *data, struct cgroup_sb_opts *opts)
> set_bit(i, &opts->subsys_bits);
> one_ss = true;
>
> - break;
> + continue;
> }
> - if (i == CGROUP_SUBSYS_COUNT)
> + if (opts->subsys_bits == 0)
> return -ENOENT;
> }
>
|
|
|
|
Goto Forum:
Current Time: Mon Nov 18 23:17:45 GMT 2024
Total time taken to generate the page: 0.03000 seconds
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
