From: Richard C Bilson <rcbilson@plg2.math.uwaterloo.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] stack reclamation on Unix using clone, rfork_thread, etc.
Date: Fri, 4 Jun 2004 12:44:50 -0400 [thread overview]
Message-ID: <200406041644.i54Giob06093@plg2.math.uwaterloo.ca> (raw)
> From: Philippe Anel <xigh@free.fr> Fri Jun 4 12:23:49 2004
>
> void
> exit_thread()
> {
> struct segment * s;
>
> lock(&addrspace);
> for (s = addrspace.tofree; s; s = s->next)
> free(s->addr);
> if (--refcount) {
> s = find_segment_from_id(get_my_thread_id());
> list_remove(s);
> list_add(tofree, s);
> }
> unlock(&addrspace);
> }
>
> ------------------------------------------------------------------------------
>
> It would free the stack of the previous exited thread.
This isn't actually so different from what Russ describes -- you're just
keeping a separate free list, rather than setting a per-thread flag in
some global list of all threads.
Note that you have to be very careful about race conditions -- your
stack could disappear immediately after the call to unlock, which means
that you'd better be done all you need to do at that point, except for
calling _exit (and even that is problematic).
next reply other threads:[~2004-06-04 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-04 16:44 Richard C Bilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-04 15:33 Richard C Bilson
2004-06-04 15:53 ` Russ Cox
2004-06-04 18:43 ` boyd, rounin
2004-06-04 16:22 ` Philippe Anel
2004-06-04 16:24 ` Philippe Anel
2004-06-04 16:38 ` Russ Cox
2004-06-04 16:43 ` Charles Forsyth
2004-06-04 19:02 ` boyd, rounin
2004-06-04 18:35 ` boyd, rounin
2004-06-04 14:39 Russ Cox
2004-06-04 15:20 ` Philippe Anel
2004-06-04 15:23 ` Philippe Anel
2004-06-04 18:30 ` boyd, rounin
2004-06-04 18:38 ` Russ Cox
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=200406041644.i54Giob06093@plg2.math.uwaterloo.ca \
--to=rcbilson@plg2.math.uwaterloo.ca \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).