From: "Chris Friesen" <cfriesen@nortel.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
vatsa@linux.vnet.ibm.com, a.p.zijlstra@chello.nl
Subject: Re: odd timing bug with cgroups -- solved
Date: Mon, 16 Jun 2008 15:29:46 -0600 [thread overview]
Message-ID: <4856DB4A.8020708@nortel.com> (raw)
In-Reply-To: <48569895.7020701@nortel.com>
Chris Friesen wrote:
> I was thinking something like this as well, like maybe we can't move the
> child to another group until it gets scheduled in once, or something
> similar.
Well, it appears I was way off base. My main task is SCHED_RR, and my
child tasks put themselves into SCHED_OTHER. I didn't have any realtime
groups configured, so it was bailing out in the first conditional in
cpu_cgroup_can_attach().
By also having the parent put the children into SCHED_OTHER, my testcase
will handle both cases (parent or child runs first) and everything seems
to be working fine.
Chris
prev parent reply other threads:[~2008-06-16 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 21:38 odd timing bug with cgroups? Chris Friesen
2008-06-14 4:15 ` Valdis.Kletnieks
2008-06-16 16:45 ` Chris Friesen
2008-06-16 21:29 ` Chris Friesen [this message]
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=4856DB4A.8020708@nortel.com \
--to=cfriesen@nortel.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=vatsa@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.