Article View: comp.sys.sequent
Article #436Re: Help with understanding of shared memory read/write on Sequent
From: Simon Marshall
Date: Wed, 30 Sep 1992 09:44
Date: Wed, 30 Sep 1992 09:44
25 lines
1428 bytes
1428 bytes
In article <1992Sep29.193203.130065@ua1ix.ua.edu> lnieplo3@ua1ix.ua.edu (Jaroslaw Nieplocha) writes:
>There are several processes reading data from a shared memory location.
>Only one process writes data, item by item. There is no explicit
>protection of the critical section.
You might try:
@book {OSTERHAUG
, author = "A. Osterhaug"
, title = "Guide to Parallel Programming on Sequent Computer Systems"
, publisher = "Prentice-Hall"
, year = "1989"
, series = "Sequent Technical Publications"
, address = "New Jersey, USA"
, edition = "second"
}
To prevent concurrent modification to shared data, you could implement your own
lock, or use one of the Sequent's own (eg. m_lock()).
Simon.
--
Simon Marshall, Dept. of Computer Science, University of Hull, Hull HU6 7RX, UK
"Football isn't about life and death. It's more important than that." Bill
Email: S.Marshall@Hull.ac.uk Phone: +44 482 465181 Fax: 466666 Shankley
Technical Details
Message-ID:
<5876@mccuts.uts.mcc.ac.uk>Path:
arc1-ca.pugleaf.net!sparky!uunet!mcsun!uknet!mucs!mccuts!ehgasm2References:
<1992Sep29.193203.130065@ua1ix.ua.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!mcsun!uknet!mucs!mccuts!ehgasm2 From: ehgasm2@uts.mcc.ac.uk (Simon Marshall) Newsgroups: comp.sys.sequent Subject: Re: Help with understanding of shared memory read/write on Sequent Message-ID: <5876@mccuts.uts.mcc.ac.uk> Date: 30 Sep 92 09:44:35 GMT References: <1992Sep29.193203.130065@ua1ix.ua.edu> Organization: Manchester Computing Centre, Manchester, England, M13 9PL. Lines: 25