digitalmars.D - Memory reordering explained by example
- deadalnix <deadalnix gmail.com> May 16 2012
- Gor Gyolchanyan <gor.f.gyolchanyan gmail.com> May 16 2012
- deadalnix <deadalnix gmail.com> May 16 2012
- Sean Cavanaugh <WorksOnMyMachine gmail.com> May 18 2012
http://preshing.com/20120515/memory-reordering-caught-in-the-act And this is why shared is important for D.
May 16 2012
--e0cb4efe325a4c111904c0253740 Content-Type: text/plain; charset=UTF-8 The problem is, that ancient processor architectures are used for modern processors and software. The correct solution to the concurrency problems would be a new architecture, designed to naturally deal with concurrency. On Wed, May 16, 2012 at 12:44 PM, deadalnix <deadalnix gmail.com> wrote:http://preshing.com/20120515/**memory-reordering-caught-in-**the-act<http://preshing.com/20120515/memory-reordering-caught-in-the-act> And this is why shared is important for D.
-- Bye, Gor Gyolchanyan. --e0cb4efe325a4c111904c0253740 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable The problem is, that ancient processor architectures are used for modern pr= ocessors and software.<div>The correct solution to the concurrency problems= would be a new architecture, designed to naturally deal with concurrency.<= /div> <div><br><div class=3D"gmail_quote">On Wed, May 16, 2012 at 12:44 PM, deada= lnix <span dir=3D"ltr"><<a href=3D"mailto:deadalnix gmail.com" target=3D= "_blank">deadalnix gmail.com</a>></span> wrote:<br><blockquote class=3D"= gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-= left:1ex"> <a href=3D"http://preshing.com/20120515/memory-reordering-caught-in-the-act= " target=3D"_blank">http://preshing.com/20120515/<u></u>memory-reordering-c= aught-in-<u></u>the-act</a><br> <br> And this is why shared is important for D.<br> </blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Bye,<br>Gor = Gyolchanyan.<br> </div> --e0cb4efe325a4c111904c0253740--
May 16 2012
Le 16/05/2012 12:59, Gor Gyolchanyan a écrit :The problem is, that ancient processor architectures are used for modern processors and software. The correct solution to the concurrency problems would be a new architecture, designed to naturally deal with concurrency. On Wed, May 16, 2012 at 12:44 PM, deadalnix <deadalnix gmail.com <mailto:deadalnix gmail.com>> wrote: http://preshing.com/20120515/__memory-reordering-caught-in-__the-act <http://preshing.com/20120515/memory-reordering-caught-in-the-act> And this is why shared is important for D. -- Bye, Gor Gyolchanyan.
It have a very high cost to do so. It would prevent many thead local optimization and, in practice, most data are thread local. It isn't a good idea. We need languages and frameworks that deal with that.
May 16 2012
On 5/16/2012 5:59 AM, Gor Gyolchanyan wrote:The problem is, that ancient processor architectures are used for modern processors and software. The correct solution to the concurrency problems would be a new architecture, designed to naturally deal with concurrency.
We have them, they are called GPUs
May 18 2012









deadalnix <deadalnix gmail.com> 