Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail
From: "Chris M. Thomasson" <no@spam.invalid>
Newsgroups: comp.programming.threads,comp.programming
Subject: Re: Intel SCC 48-core x86 Processor
Date: Wed, 19 Jun 2013 18:57:57 -0700
Organization: Aioe.org NNTP Server
Lines: 29
Message-ID: <kptnja$pgb$1@speranza.aioe.org>
References: <kptfbn$cco$1@dont-email.me> <kptjeo$tkt$1@dont-email.me> <kptk4l$i2f$1@speranza.aioe.org> <51C284DA.4040307@toto.net>
NNTP-Posting-Host: PomiWpvG4e2y0HvOhU0dhw.user.speranza.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308
X-Notice: Filtered by postfilter v. 0.8.2
X-Newsreader: Microsoft Windows Live Mail 15.4.3555.308
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
Xref: csiph.com comp.programming.threads:1567 comp.programming:3471


"aminer"  wrote in message news:51C284DA.4040307@toto.net...


> Hello,

> I don't understand something:

> Look at this:

> "wait_for_all_readers_notifications();"

> How can you wait for all the readers ? this algorithm
> do not tell us how to wait for all the readers ?

Yikes! I posted to a brief overall sketch of the algorithm.

Check this for more a more detailed sketch:

https://groups.google.com/forum/?fromgroups#!original/comp.programming.threads/t9O4wI-co8Y/ya3QnzvbajUJ

Sorry about that Aminer.

Anyway, this is one way to do it, e.g., iterate and observe
reader state in writer before the key aspect of asymmetric
memory synchronization actually kicks in...

http://home.comcast.net/~pjbishop/Dave/Asymmetric-Dekker-Synchronization.txt