From: Oleg Nesterov <oleg@tv-sign.ru>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Gautham R Shenoy <ego@in.ibm.com>, Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC,PATCH 5/5] exec: RT sub-thread can livelock and monopolize CPU on exec
Date: Sun, 19 Aug 2007 12:38:27 +0400 [thread overview]
Message-ID: <20070819083827.GA83@tv-sign.ru> (raw)
In-Reply-To: <20070818232525.9B7554D05C6@magilla.localdomain>
On 08/18, Roland McGrath wrote:
>
> Maybe it can use wait_task_inactive, which IIUC is being changed to address
> the same RT issue.
The group_leader can sleep before it enters exit_notify(). In that case
wait_task_inactive() returns, and we still need some polling to wait for
EXIT_ZOMBIE.
> OTOH, notify_count exists only for this. So maybe the
> better way is to clean that whole mechanism up somehow.
Yes sure. But in any case I think we should avoid polling, we need some
notification from exit_notify().
> The exit.c changes
> in your patch seem to be making it more mysterious rather than less so.
I completely agree.
Oleg.
next prev parent reply other threads:[~2007-08-19 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-18 17:40 [RFC,PATCH 5/5] exec: RT sub-thread can livelock and monopolize CPU on exec Oleg Nesterov
2007-08-18 23:25 ` Roland McGrath
2007-08-19 8:38 ` Oleg Nesterov [this message]
2007-08-19 19:45 ` Roland McGrath
2007-08-19 20:10 ` Oleg Nesterov
2007-08-19 20:31 ` Roland McGrath
2007-08-20 15:07 ` Oleg Nesterov
2007-08-28 8:54 ` Roland McGrath
2007-08-28 10:01 ` Oleg Nesterov
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=20070819083827.GA83@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=torvalds@linux-foundation.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