From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] shared memory
Date: Fri, 12 Sep 2003 01:48:43 -0700 [thread overview]
Message-ID: <b289e9a8b60b6340c2311480d6c8f747@collyer.net> (raw)
In-Reply-To: <4763ae131a392f86049a4313ff09683c@granite.cias.osakafu-u.ac.jp>
It exists. segattach(2) and rfork(2) should get you started. You'll
want to use lock(2), rendezvous(2), or thread(2) to coordinate access.
pool(2) can be used to allocate pieces of it.
next prev parent reply other threads:[~2003-09-12 8:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 5:32 [9fans] g++ YAMANASHI Takeshi
2003-09-12 7:25 ` okamoto
2003-09-12 9:29 ` northern snowfall
2003-09-12 8:33 ` okamoto
2003-09-12 8:43 ` [9fans] shared memory okamoto
2003-09-12 8:48 ` Geoff Collyer [this message]
2003-09-12 8:52 ` okamoto
2003-09-12 9:25 ` Geoff Collyer
2003-09-12 9:30 ` Charles Forsyth
2003-09-12 15:33 ` splite
2003-09-12 16:11 ` boyd, rounin
2003-09-12 12:12 ` David Presotto
2003-09-16 3:07 ` okamoto
2003-09-15 13:30 ` okamoto
2003-09-16 4:23 ` Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2002-07-29 11:13 paurea
2002-07-29 13:56 ` Ronald G Minnich
2002-07-29 13:59 ` Ronald G Minnich
2002-07-31 12:52 ` andrey mirtchovski
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=b289e9a8b60b6340c2311480d6c8f747@collyer.net \
--to=geoff@collyer.net \
--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).