From: Florian Philipp <lists@f_philipp.fastmail.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] cgroupd really do work!
Date: Mon, 06 Dec 2010 05:51:44 +0100 [thread overview]
Message-ID: <4CFC6BE0.4060309@f_philipp.fastmail.net> (raw)
In-Reply-To: <AANLkTikKFjhPXvPXSWiXOCAY4kkkFmcBA385mB4mCPPt@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1455 bytes --]
Am 06.12.2010 00:54, schrieb Bill Longman:
>
>
> Hmm, I just noticed that something is not right here: Everything works
> fine as long as I limit the cgroups to cpu scheduling (`mount -t cgroup
> cgroup /dev/cgroup -o cpu`). As soon as I add the blkio subsystem for
> disk I/O scheduling ("-o cpu,blkio" or no "-o" at all), I can no longer
> create cgroup hierarchies. Only the top level "user" cgroup is accepted.
>
> Another issue is that the kernel documentation in
> /usr/src/linux/Documentation/cgroups/cgroups.txt specifies that the
> release_agent can also be included as a mount option with
> `mount -t cgroup cgroup /dev/cgroup -o
> cpu,release_agent='/usr/local/sbin/cgroup_clean'`
> That seems to be no valid option, though. At least on my system it
> causes mount to fail. Unfortunately there is no output on dmesg.
>
> Can someone else reproduce this? I'm on gentoo-sources-2.6.34-r12.
>
>
> I had this very same problem when I was trying this last year, Florian.
> I didn't pursue it any further so I can't tell you any solutions. I do
> remember it though because it was quite frustrating.
>
> --
> Bill Longman
Thanks for the answer!
I think I've found the answer, at least for the first issue: Look at
this bug: https://bugzilla.kernel.org/show_bug.cgi?id=15980
I still don't know what causes the second issue.
Regards,
Florian Philipp
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2010-12-06 4:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 0:41 [gentoo-user] cgroupd really do work! William Kenworthy
2010-12-04 1:20 ` Mark Knecht
2010-12-04 2:16 ` William Kenworthy
2010-12-04 21:00 ` Mark Knecht
2010-12-05 14:55 ` Florian Philipp
2010-12-05 15:35 ` Mark Knecht
2010-12-05 16:02 ` Florian Philipp
2010-12-05 23:54 ` Bill Longman
2010-12-06 4:51 ` Florian Philipp [this message]
2010-12-06 20:04 ` [gentoo-user] " Doug Hunley
2010-12-06 20:44 ` Doug Hunley
2010-12-06 22:00 ` Florian Philipp
2010-12-07 5:51 ` [gentoo-user] " Scott Prager
2010-12-07 8:43 ` Neil Bothwick
2010-12-04 19:52 ` [gentoo-user] " walt
2010-12-05 1:10 ` William Kenworthy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CFC6BE0.4060309@f_philipp.fastmail.net \
--to=lists@f_philipp.fastmail.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox