Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #73566
| References | <53a8d31f$0$29988$c3e8da3$5496439d@news.astraweb.com> <lobm4g$u05$1@news.albasani.net> <53aa6381$0$11121$c3e8da3@news.astraweb.com> <c0vc69Fjg3rU1@mid.individual.net> |
|---|---|
| Date | 2014-06-25 17:46 +1000 |
| Subject | Re: Off-Topic: The Machine |
| From | Chris Angelico <rosuav@gmail.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.11231.1403682390.18130.python-list@python.org> (permalink) |
On Wed, Jun 25, 2014 at 5:31 PM, Gregory Ewing <greg.ewing@canterbury.ac.nz> wrote: > That's nice, but the question that comes to my mind is: > What happens when a zillion cores are all competing for > high-speed access to that memory? And what happens if some of those cores are corrupt? Can you initiate a core transfer? Will there be a stalemate? Are there any trained Stalemate Resolution Associates around? What if there's a fire in the Stalemate Resolution Annex? Seriously, though, how would you go about debugging a system so massively parallel? If most of the CPU cores are special-purpose, it's going to require a whole new method of testing. I can just imagine configure scripts having to be taught to cope with a new form of CPU bug (in the same way that some still test for the Pentium division bug). ChrisA
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
Off-Topic: The Machine Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2014-06-24 01:23 +0000
Re: Off-Topic: The Machine Johannes Bauer <dfnsonfsduifb@gmx.de> - 2014-06-24 13:06 +0200
Re: Off-Topic: The Machine Steven D'Aprano <steve@pearwood.info> - 2014-06-25 05:52 +0000
Re: Off-Topic: The Machine Chris Angelico <rosuav@gmail.com> - 2014-06-25 16:06 +1000
Re: Off-Topic: The Machine Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-06-25 19:31 +1200
Re: Off-Topic: The Machine Chris Angelico <rosuav@gmail.com> - 2014-06-25 17:46 +1000
csiph-web