public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at physics dot uc dot edu" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/29324] add wait handling hook
Date: Thu, 05 Oct 2006 05:48:00 -0000	[thread overview]
Message-ID: <20061005054855.9447.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29324-360@http.gcc.gnu.org/bugzilla/>



------- Comment #4 from pinskia at physics dot uc dot edu  2006-10-05 05:48 -------
Subject: Re:  add wait handling hook

On Thu, 2006-10-05 at 05:42 +0000, daney at gcc dot gnu dot org wrote:
> 
> ------- Comment #3 from daney at gcc dot gnu dot org  2006-10-05 05:42 -------
> One way to fix it would be to have a reaper thread for *each* Process.  Then
> the reaper could do a waitpid(pid...) instead of waitpid(-1...).  If one only
> spawns a few processes, this would be fine.  This would allow us to get rid of
> the SIGCHLD handler as well.
> 
> Another option would to have the process reaper be a seperate process, but that
> scares me.

Even multiple threads scares me for Linux since that would mean double
the amount of processes in the process table.  Maybe Linux needs this
problem if it still exists.  I know Linux threads had this problem but I
forget if NTPL does.

Thanks,
Andrew Pinski


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29324


  parent reply	other threads:[~2006-10-05  5:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02 18:01 [Bug libgcj/29324] New: " tromey at gcc dot gnu dot org
2006-10-02 18:35 ` [Bug libgcj/29324] " pinskia at gcc dot gnu dot org
2006-10-02 18:39 ` tromey at gcc dot gnu dot org
2006-10-05  5:42 ` daney at gcc dot gnu dot org
2006-10-05  5:48 ` pinskia at physics dot uc dot edu [this message]
2006-10-05 17:02 ` daney at gcc dot gnu dot org
2006-10-05 17:24 ` daney at gcc dot gnu dot org
2007-05-12 17:38 ` daney at gcc dot gnu dot org
2007-05-12 18:52 ` daney at gcc dot gnu dot org

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=20061005054855.9447.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).