mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dirk Bull" <dirkbull102@hotmail.com>
To: fork0@users.sf.net, doug@mcnaught.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: shmat problem
Date: Tue, 07 Jan 2003 08:14:17 +0000	[thread overview]
Message-ID: <F39ekoL0jfQnPEiuGHi0001ee0c@hotmail.com> (raw)

Thanks for your help. I also thought the memory mapping code I'm
porting looked funny. The code forms part of a simulation program where a 
few processes have to share data in a data base. In the code they(the 
original implementers) initialize a bunch of variables and then share these 
variables as I've shown you. I've referenced W.R Stevens's UNIX programming 
books and found no information on whether you could share memory other than 
that on the heap (did not want to change their code to use pointers, not a 
good idea to change too much of the original code). To end a long story, 
Alex, thanks for the SHM_REMAP flag, would never have found it, you've saved 
me a lot of time. Finally, in the code they share pages, therefor using 
SHM_REMAP is not that unsafe, but still not good practice?

Thanks again.

Dirk









_________________________________________________________________
Help STOP SPAM: Try the new MSN 8 and get 2 months FREE* 
http://join.msn.com/?page=features/junkmail


             reply	other threads:[~2003-01-07  8:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-07  8:14 Dirk Bull [this message]
2003-01-07 18:41 ` Alex Riesen
  -- strict thread matches above, loose matches on Subject: below --
2003-01-06 16:22 Alex Riesen
2003-01-06 16:36 ` Doug McNaught
2003-01-06 16:43   ` Alex Riesen
2003-01-06 16:50     ` Doug McNaught
2003-01-06 17:01       ` Alex Riesen
2003-01-06 14:53 Dirk Bull
2003-01-06 15:32 ` Doug McNaught
2003-01-06 15:50   ` Richard B. Johnson
2003-01-06  9:05 Dirk Bull
2003-01-06 14:17 ` Doug McNaught

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=F39ekoL0jfQnPEiuGHi0001ee0c@hotmail.com \
    --to=dirkbull102@hotmail.com \
    --cc=doug@mcnaught.org \
    --cc=fork0@users.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®