Richard Braun, le Mon 18 Nov 2013 00:36:14 +0100, a écrit :
> On Sun, Nov 17, 2013 at 09:41:03PM +0100, Samuel Thibault wrote:
> > Richard Braun, le Sun 17 Nov 2013 17:13:23 +0100, a écrit :
> > > This patch makes use of a new GNU Mach specific call
> > > (thread_terminate_release [1]) so that thre
At Mon, 18 Nov 2013 16:14:57 +0100,
Samuel Thibault wrote:
>
> Neal H. Walfield, le Mon 18 Nov 2013 13:41:46 +0100, a écrit :
> > At Mon, 18 Nov 2013 12:31:42 +0100,
> > Richard Braun wrote:
> > > The threading library is a
> > > low level component and should act as closely as its users expect it
On Mon, Nov 18, 2013 at 04:22:06PM +0100, Samuel Thibault wrote:
> Richard Braun, le Sun 17 Nov 2013 17:13:23 +0100, a écrit :
> > Two resources are still recycled: the internal pthread structure
> > (because it makes ID allocation easy), and thread local storage (TLS)
> > because that's where the
Richard Braun, le Sun 17 Nov 2013 17:13:23 +0100, a écrit :
> Two resources are still recycled: the internal pthread structure
> (because it makes ID allocation easy), and thread local storage (TLS)
> because that's where the reply port is stored, and it didn't seem
> convenient to call _dl_dealloc
Neal H. Walfield, le Mon 18 Nov 2013 13:41:46 +0100, a écrit :
> At Mon, 18 Nov 2013 12:31:42 +0100,
> Richard Braun wrote:
> > The threading library is a
> > low level component and should act as closely as its users expect it to.
>
> I don't agree. On Linux, creating a thread is a pretty much a
At Mon, 18 Nov 2013 12:31:42 +0100,
Richard Braun wrote:
>
> On Mon, Nov 18, 2013 at 11:33:55AM +0100, Neal H. Walfield wrote:
> > Richard Braun wrote:
> > > The current state is to never terminate threads, on the assumption that
> > > they can't both terminate and release their stack on their own
On Mon, Nov 18, 2013 at 11:33:55AM +0100, Neal H. Walfield wrote:
> Richard Braun wrote:
> > The current state is to never terminate threads, on the assumption that
> > they can't both terminate and release their stack on their own. Such
> > resources are recycled by the threading library. This pa
At Sun, 17 Nov 2013 17:13:23 +0100,
Richard Braun wrote:
> The current state is to never terminate threads, on the assumption that
> they can't both terminate and release their stack on their own. Such
> resources are recycled by the threading library. This patch makes use
> of a new GNU Mach spec
On Sun, Nov 17, 2013 at 05:13:23PM +0100, Richard Braun wrote:
> The following changes actually apply to Debian eglibc 2.17-96 sources,
Binary packages are available for testing on my repository :
deb http://ftp.sceen.net/debian-hurd-i386 experimental/
Install gnumach first, then glibc, then the
On Sun, Nov 17, 2013 at 09:41:03PM +0100, Samuel Thibault wrote:
> Richard Braun, le Sun 17 Nov 2013 17:13:23 +0100, a écrit :
> > This patch makes use of a new GNU Mach specific call
> > (thread_terminate_release [1]) so that threads do terminate themselves
> > and release their stack, and in addi
Hello,
Richard Braun, le Sun 17 Nov 2013 17:13:23 +0100, a écrit :
> This patch makes use of a new GNU Mach specific call
> (thread_terminate_release [1]) so that threads do terminate themselves
> and release their stack, and in addition their last self reference,
> and their reply port.
I was fi
The following changes actually apply to Debian eglibc 2.17-96 sources,
and aren't meant to be pushed as such, but rather to review the various
solutions added to support thread termination.
The current state is to never terminate threads, on the assumption that
they can't both terminate and releas
12 matches
Mail list logo
