realbasic-nug
[Top] [All Lists]

Re: Dealing with multi-processor or multi-core (shared memory semi solut

To: REALbasic NUG <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: Dealing with multi-processor or multi-core (shared memory semi solution)
From: Norman Palardy <npalardy at great-white-software dot com>
Date: Fri, 30 May 2008 15:46:17 -0600
Authentication-results: mx.google.com; spf=pass (google.com: domain of realbasic-nug-bounces at lists dot realsoftware dot com designates 66.116.103.65 as permitted sender) smtp dot mail=realbasic-nug-bounces at lists dot realsoftware dot com
Delivered-to: listarchive at realsoftware dot com
Delivered-to: realbasic-nug at lists dot realsoftware dot com
References: <77124270805301112ja025ec1i5295f790cf52d33b at mail dot gmail dot com> <BAY107-DAV13E1BCBA0B8DD7A3965E3D93BE0 at phx dot gbl> <77124270805301302v4b6f531by1501155ebce893f at mail dot gmail dot com> <298EE353-3AE8-4792-B9D1-2E199601FBFE at mac dot com> <A2A4DD56-8DD5-44AB-8051-4129D48690B0 at declareSub dot com>
On 30-May-08, at 3:37 PM, Charles Yeomans wrote:

>
> This is all the easy part.  The hard part is synchronized access to
> the shared data.
>
> Charles Yeomans

Possibly better to wrap the shm_xxx functions
        shm_open(2)              - open a shared memory object
        shm_unlink(2)            - remove shared memory object
        shmat(2), shmdt(2)       - map/unmap shared memory
        shmctl(2)                - shared memory control operations
        shmget(2)                - get shared memory area identifier

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>