From: splite@purdue.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] shared memory
Date: Fri, 12 Sep 2003 10:33:01 -0500 [thread overview]
Message-ID: <20030912153301.GB3969@sigint.cs.purdue.edu> (raw)
In-Reply-To: <b264a90e165c80f5da8e84351220e8ae@caldo.demon.co.uk>
On Fri, Sep 12, 2003 at 10:30:57AM +0100, Charles Forsyth wrote:
> >>If you're looking for a way for unrelated processes to share memory, I
> >>think your best bet is to use the undocumented S option of ramfs:
>
> there is also segment(3), when configured.
Did anyone else read that and wonder "how do you ment a seg?"
I need more coffee. Or maybe a frosty Hires "High Resolution" root beer.
next prev parent reply other threads:[~2003-09-12 15:33 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
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 [this message]
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=20030912153301.GB3969@sigint.cs.purdue.edu \
--to=splite@purdue.edu \
--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).