Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!ucbvax!UUNET.UU.NET!mcsun!ukc!cam-cl!cet1
From: mcsun!ukc!cam-cl!cet1@UUNET.UU.NET ("C.E. Thompson")
Newsgroups: comp.lang.asm370
Subject: Re: More pet ALC tricks...
Message-ID: <8911151823.AA25006@brazos.rice.edu>
Date: 14 Nov 89 22:16:17 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: IBM 370 Assembly Programming Discussion List <ASM370%UCF1VM.BITNET@ricevm1.rice.edu>
Distribution: inet
Organization: The Internet
Lines: 16

In article <8911131336.AA27002@brazos.rice.edu>,P85025@BARILVM.BITNET (Doron
        Shikmoni) writes
>Note, that CS/CDS/TS should be used only if you really need to serialize;
>if you just want to compare-and-then-swap, and think of using these since
>"It's one instruction", in a simple "application" program, don't; these
>instructions are expensive.

Well, they are not as cheap as L and C, say, but you shouldn't be paranoid
about using them, either. On CPUs with write-in caches, the overheads are
not that bad. It makes sense to use CS/CDS to synchronise between a program
and an asynchronous exit, for example, using them for their non-divisibility
rather than their MP-storage-consistency.

Chris Thompson
JANET:    cet1@uk.ac.cam.phx
Internet: cet1%phx.cam.ac.uk@nsfnet-relay.ac.uk