From: Joel Salomon <chesky@plan9.jp>
To: 9fans@cse.psu.edu
Subject: [9fans] Creating a custom jmp_buf; libthread implementation question
Date: Mon, 13 Nov 2006 22:23:17 -0500 [thread overview]
Message-ID: <64c8196ab25721b971e64c96b6f8e065@plan9.jp> (raw)
For my next homework in my Operating Systems class, the professor has
assigned the equivalent of a simple libthread. I’ve been looking
through the libthread code and getting lost ☹. I don’t need procs,
only threads (except for the oh-so-fun complication of user-level
pre-emptive scheduling, but I can worry about that mañana). I do,
however, need to create per-thread stacks, probably by massaging
jmp_bufs in malloc()ed memory.
Where in libthread does the stack get set up, and could somebody
please give me a high-level overview of what the code is doing?
Thanks, --Joel
next reply other threads:[~2006-11-14 3:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 3:23 Joel Salomon [this message]
2006-11-14 3:33 ` Joel Salomon
2006-11-14 9:39 ` Bruce Ellis
2006-11-14 12:34 ` Russ Cox
2006-11-14 16:15 ` Joel Salomon
2006-11-21 3:03 ` Joel Salomon
2006-11-21 3:03 ` William Josephson
2006-11-21 3:08 ` Russ Cox
2006-11-14 9:58 ` Gorka guardiola
2006-11-14 16:25 ` Joel Salomon
2006-11-14 16:38 ` Joel Salomon
2006-11-14 19:44 ` Taj Khattra
2006-11-14 5:44 ` [9fans] Skip Tavakkolian
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=64c8196ab25721b971e64c96b6f8e065@plan9.jp \
--to=chesky@plan9.jp \
--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).