Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (athena.apache.org: domain of liyilei1979@gmail.com
 designates 209.85.128.191 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=opzZ4nOGywoZPUBCWrBoklBAWZD4Ck5TXPprcgUcA/wXUiszz2efCDB8k094FBzn6KNf0kEmMffz5jrngFqVDx/Ob1hZoIty9rLOIYJVBRHQSfJx71wJFvN6F5yrSb/2rWMgSSDbCHaT+83rwbT25oByHIZVKBoNRKlQLCoDkiM=
Message-ID: <e66844de0709142035h7863dc27p3ac5adcec2aabfdb@mail.gmail.com>
Date: Sat, 15 Sep 2007 11:35:00 +0800
From: "Leo Li" <liyilei1979@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [classlib] Shared Memory
In-Reply-To: <46EADA63.9060300@qnx.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <46EADA63.9060300@qnx.com>

On 9/15/07, Rodney Dowdall <rdowdall@qnx.com> wrote:

> Hello
>
> Please forgive my ignorance, but I am not certain on how the Unix
> shmget, shmat, shmdt functions work.  I am trying to port the classlib
> to QNX Neutrino, which uses shm_open, shm_ctl and shm_unlink.  In the
> shared memory code a control file is created, and then a key is
> generated using ftok with the control file name.  Control file data is
> then written to the control file.  When you do a shmat is the shared

  Hi, Rodney:

  Excuse me, are you trying to use a shared memory file as the control file?

> memory attaching to the file?  Or is it a clean area in memory?  I'm

    If you transfer a NULL parameter as the target address for shmat,
System will choose a proper block( and not allocated ) of virtual
memory space into which the shared memory will be mapped.

> wondering if I have to generate a new name for my shm_open call, or if I
> can just use the control file name.

    If you want shm_open to get different shared memory objects, it is
necessary to use distinct names. Although shm_open will return
different fid by the same name, the fid will reference the same shared
memory objects. Furthermore, the shared object is system wide and will
last till next boot or explicitly call shm_unlink if I have not missed
something.

>
> Thanks,
> Rodney
>


-- 
Leo Li
China Software Development Lab, IBM