home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.realtime
- Path: sparky!uunet!psinntp!hns!sharpster
- From: sharpster@hns.com (Stephen Harpster)
- Subject: Re: Shared memory access under 1003.4?
- Message-ID: <1992Aug17.130636.5184@hns.com>
- Originator: sharpster@sharpster
- Sender: news@hns.com (USENET news system)
- Organization: Hughes Network Systems
- References: <17285@vd.seqeb.gov.au>
- Distribution: hns
- Date: Mon, 17 Aug 1992 13:06:36 GMT
- Lines: 14
-
-
- In article <17285@vd.seqeb.gov.au>, BSS_MIKE@vd.seqeb.gov.au writes:
- |> Is access to shared memory covered by 1003.4?
-
- Yes.
-
- |> If so, how is identification of a region currently being proposed - via a
- |> numeric identifier as per System 5, or by a name as per VMS. Presumably once
- |> accessed, a handle would then be used for efficiency?
-
- According to Draft 10, it's a "nonnegative integer representing the
- lowest numbered unused file descriptor." The prototype is
-
- extern int shm_open(const char *path, int oflag, mode_t mode);
-