From: Andrew Cagney <cagney@gnu.org>
To: Daniel Jacobowitz <drow@false.org>
Cc: Jeff Johnston <jjohnstn@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [RFC]: fix for recycled thread ids
Date: Fri, 19 Mar 2004 20:33:00 -0000 [thread overview]
Message-ID: <405B591F.10805@gnu.org> (raw)
In-Reply-To: <20040319015351.GA28443@nevyn.them.org>
> On Thu, Mar 18, 2004 at 07:36:25PM -0500, Jeff Johnston wrote:
>
>>> The following patch fixes a problem when a user application creates a
>>> thread shortly after another thread has completed. For nptl, thread ids
>>> are addresses. If a thread completes/dies, the tid is available for reuse
>>> by a new thread.
>
>
> Does NPTL re-use the TID quickly, or cycle around the way LT did so
> that we only see this under high thread pressure?
Immediatly. Since they are pointers NPTL re-cycles them as soon as they
are freed (on the next thread create and, obviously, in preference to
allocating a new buffer) -- very different to the linuxthreads model.
As a consequence any heavily threaded app quickly shows the problem -
java (esp eclipse) for instance.
Andrew
prev parent reply other threads:[~2004-03-19 20:33 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:36 Jeff Johnston
2004-03-19 1:53 ` Daniel Jacobowitz
2004-03-19 18:44 ` Jeff Johnston
2004-03-19 19:01 ` Daniel Jacobowitz
2004-03-19 19:35 ` Jeff Johnston
2004-03-19 19:40 ` Daniel Jacobowitz
2004-03-19 21:32 ` Jeff Johnston
2004-03-24 15:51 ` Daniel Jacobowitz
2004-03-24 16:56 ` Daniel Jacobowitz
2004-03-24 21:56 ` Jeff Johnston
2004-03-25 0:46 ` Jeff Johnston
2004-03-25 4:39 ` Daniel Jacobowitz
2004-03-25 16:34 ` Daniel Jacobowitz
2004-03-25 20:22 ` Jeff Johnston
2004-03-26 17:59 ` [patch] Use TD_DEATH and PTRACE_EVENT_CLONE when available (was: Re: [RFC]: fix for recycled thread ids) Daniel Jacobowitz
2004-03-26 18:14 ` [patch] Use TD_DEATH and PTRACE_EVENT_CLONE when available Jeff Johnston
2004-03-26 21:13 ` [patch] New thread test to exercise Daniel's Patch Jeff Johnston
2004-03-26 21:19 ` Daniel Jacobowitz
2004-03-29 18:06 ` Jeff Johnston
2004-03-29 18:11 ` Daniel Jacobowitz
2004-03-29 20:18 ` Jeff Johnston
2004-03-29 20:42 ` Daniel Jacobowitz
2004-03-29 21:04 ` Jeff Johnston
2004-03-29 21:34 ` Daniel Jacobowitz
2004-03-29 21:59 ` Jeff Johnston
2004-03-29 22:32 ` Daniel Jacobowitz
2004-03-29 22:58 ` Jeff Johnston
2004-03-29 23:57 ` Daniel Jacobowitz
2004-03-29 18:07 ` [patch] Use TD_DEATH and PTRACE_EVENT_CLONE when available (was: Re: [RFC]: fix for recycled thread ids) Daniel Jacobowitz
2004-03-19 20:33 ` Andrew Cagney [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=405B591F.10805@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@redhat.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