Path: csiph.com!usenet.pasdenom.info!aioe.org!news.stack.nl!newsfeed.xs4all.nl!newsfeed2a.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.063 X-Spam-Evidence: '*H*': 0.90; '*S*': 0.03; 'scripts': 0.03; 'configure': 0.05; 'debugging': 0.07; 'cc:addr:python-list': 0.11; 'bug': 0.12; 'bug).': 0.16; 'from:addr:rosuav': 0.16; 'from:name:chris angelico': 0.16; 'massively': 0.16; 'pentium': 0.16; 'wrote:': 0.18; 'wed,': 0.18; '(in': 0.22; 'cc:addr:python.org': 0.22; 'question': 0.24; 'cc:2**0': 0.24; 'header:In-Reply-To:1': 0.27; 'resolution': 0.29; 'message- id:@mail.gmail.com': 0.30; '25,': 0.31; 'division': 0.31; 'initiate': 0.31; 'testing.': 0.31; 'core': 0.34; 'test': 0.35; 'but': 0.35; 'received:google.com': 0.35; 'there': 0.35; 'method': 0.36; 'pm,': 0.38; 'though,': 0.39; 'how': 0.40; 'associates': 0.60; 'most': 0.60; 'new': 0.61; 'subject:The': 0.64; 'fire': 0.65; 'nice,': 0.84; 'seriously,': 0.84; 'to:none': 0.92; 'imagine': 0.93; 'subject:Topic': 0.95; 'trained': 0.95; 'taught': 0.96 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type; bh=x8QpPQpuk+jMxdsTrIBZl5ZDdNRHGAvvQzodiyh/hNs=; b=glVA/N+7e0V+Md6++YafUDAfIgTjXxmmOZh1Ttnc2sHYU6I72swrMFnCgxe5uOLTJm sypBPW119WeJNmizfIv2js4lXwv6m4s6wR8l5SLddiK70TvJX8MRp43+PY2Fp/GNk6IV 19TGPUW2NfExRzAebjt7i94BYBvOnguIXUtr5RzuNkFi6gdKKDTNXzd2bjQzvZKrGWiu RvpwF/uWgwIR2YSIf1mekKT1Uw7khSGq0Cc57gZN1Utaec9NHC7U8k0VpogMKppqUL8Y OHOtNvNqgDp/yxqyUxkPAISoAx9s/06jsyS2YLSgZhBkQp0i1jE6EN5Z8r1ZlVNi351K 7fCg== MIME-Version: 1.0 X-Received: by 10.220.69.72 with SMTP id y8mr5415499vci.21.1403682382320; Wed, 25 Jun 2014 00:46:22 -0700 (PDT) In-Reply-To: References: <53a8d31f$0$29988$c3e8da3$5496439d@news.astraweb.com> <53aa6381$0$11121$c3e8da3@news.astraweb.com> Date: Wed, 25 Jun 2014 17:46:22 +1000 Subject: Re: Off-Topic: The Machine From: Chris Angelico Cc: "python-list@python.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 19 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1403682390 news.xs4all.nl 2941 [2001:888:2000:d::a6]:53318 X-Complaints-To: abuse@xs4all.nl Xref: csiph.com comp.lang.python:73566 On Wed, Jun 25, 2014 at 5:31 PM, Gregory Ewing 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