By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,672 Members | 1,300 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,672 IT Pros & Developers. It's quick & easy.

Using the backing store with mmap

P: n/a
According to the mmap.mmap 2.5 documentation,
"Changed in version 2.5: To map anonymous memory, -1 should be passed
as the fileno along with the length."

I would like to use shared memory to communicate between two processes
that otherwise have no way to communicate, but I couldn't find a way
to share anonymous memory. (I can use file names agreed on by
convention, but the file is really irrelevant, and I'd prefer to
eliminate it.) Is this possible? What is the lifetime of this shared
memory? Is it in fact private to the creating process, or is it
shared among all (Python) processes? Does it need to be flushed by a
writing process? How do the access flags relate to this? If I create
two such items, are they independent, or is it all one pool?

TIA,
Jon Peck
Jun 27 '08 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.