From: Valdis.Kletnieks@vt.edu
To: Chris Friesen <cfriesen@nortel.com>
Cc: linux-kernel@vger.kernel.org, vatsa@linux.vnet.ibm.com,
a.p.zijlstra@chello.nl
Subject: Re: odd timing bug with cgroups?
Date: Sat, 14 Jun 2008 00:15:31 -0400 [thread overview]
Message-ID: <47364.1213416931@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 13 Jun 2008 15:38:29 MDT." <4852E8D5.3000503@nortel.com>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Fri, 13 Jun 2008 15:38:29 MDT, Chris Friesen said:
> This seems odd...I would think that as soon as the fork() call returns
> in the parent we should be able to put that task into a group.
I'm admittedly shooting in the dark here, but remember that a successful
fork() call returns *twice*. Just because the *parent* has returned
doesn't mean that the *child* has finished all the processing and returned
as well - it may be delayed by other kernel threads etc and still not quite
ready for tweaking.
It sounds like a variant of the race conditions we had a while back where
lots of programs blew chunks when we started having "child runs first"
semantics so children could run and exit before the parent was ready
for it?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-06-14 4:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 21:38 Chris Friesen
2008-06-14 4:15 ` Valdis.Kletnieks [this message]
2008-06-16 16:45 ` Chris Friesen
2008-06-16 21:29 ` odd timing bug with cgroups -- solved Chris Friesen
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=47364.1213416931@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=a.p.zijlstra@chello.nl \
--cc=cfriesen@nortel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®