* [9fans] tprivalloc, tprivfree, tprivaddr
@ 2012-12-01 23:42 erik quanstrom
2012-12-02 11:24 ` Charles Forsyth
0 siblings, 1 reply; 2+ messages in thread
From: erik quanstrom @ 2012-12-01 23:42 UTC (permalink / raw)
To: 9fans
the thread library has these undocumented functions.
what doesn't make sense to me is the allocation tracking is global,
while the pointers are per-thread Thread.udata[].
what's going on here? it would seem to me that the easiest way to
clean this up would be to make the allocated mask part of the thread
structure, if i've got the reasoning behind these functions correct.
why do we also have threaddata?
do we just leak the data if we kill the thread?
on my system at least, none of this is used.
- erik
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [9fans] tprivalloc, tprivfree, tprivaddr
2012-12-01 23:42 [9fans] tprivalloc, tprivfree, tprivaddr erik quanstrom
@ 2012-12-02 11:24 ` Charles Forsyth
0 siblings, 0 replies; 2+ messages in thread
From: Charles Forsyth @ 2012-12-02 11:24 UTC (permalink / raw)
To: Fans of the OS Plan 9 from Bell Labs
It's to allocate global names (indices) with per-thread values.
On 1 December 2012 23:42, erik quanstrom <quanstro@quanstro.net> wrote:
> what doesn't make sense to me is the allocation tracking is global,
> while the pointers are per-thread Thread.udata[].
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-12-02 11:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-12-01 23:42 [9fans] tprivalloc, tprivfree, tprivaddr erik quanstrom
2012-12-02 11:24 ` Charles Forsyth
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).