From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7854 invoked by alias); 19 Mar 2004 20:33:37 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 7847 invoked from network); 19 Mar 2004 20:33:36 -0000 Received: from unknown (HELO localhost.redhat.com) (66.30.197.194) by sources.redhat.com with SMTP; 19 Mar 2004 20:33:36 -0000 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 7DB572B92; Fri, 19 Mar 2004 15:33:35 -0500 (EST) Message-ID: <405B591F.10805@gnu.org> Date: Fri, 19 Mar 2004 20:33:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040217 MIME-Version: 1.0 To: Daniel Jacobowitz Cc: Jeff Johnston , gdb-patches@sources.redhat.com Subject: Re: [RFC]: fix for recycled thread ids References: <405A4089.1080605@redhat.com> <20040319015351.GA28443@nevyn.them.org> In-Reply-To: <20040319015351.GA28443@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-03/txt/msg00471.txt.bz2 > 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