From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] tprivalloc, tprivfree, tprivaddr
Date: Sat, 1 Dec 2012 18:42:53 -0500 [thread overview]
Message-ID: <88df240d06e36e23de6dfb42140907e2@brasstown.quanstro.net> (raw)
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
next reply other threads:[~2012-12-01 23:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-01 23:42 erik quanstrom [this message]
2012-12-02 11:24 ` Charles Forsyth
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=88df240d06e36e23de6dfb42140907e2@brasstown.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).