Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752255AbWKLSQo (ORCPT ); Sun, 12 Nov 2006 13:16:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752250AbWKLSQn (ORCPT ); Sun, 12 Nov 2006 13:16:43 -0500 Received: from gprs189-60.eurotel.cz ([160.218.189.60]:62988 "EHLO spitz.ucw.cz") by vger.kernel.org with ESMTP id S1752129AbWKLSQn (ORCPT ); Sun, 12 Nov 2006 13:16:43 -0500 Date: Sun, 12 Nov 2006 14:28:13 +0000 From: Pavel Machek To: Mikulas Patocka Cc: Albert Cahalan , linux-kernel@vger.kernel.org Subject: Re: 2048 CPUs [was: Re: New filesystem for Linux] Message-ID: <20061112142813.GA4371@ucw.cz> References: <787b0d920611041154l69db46abv4c8c467809ada57c@mail.gmail.com> <20061107212614.GA6730@ucw.cz> <20061107231456.GB7796@elf.ucw.cz> <20061110090303.GB3196@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1044 Lines: 33 Hi! > >>You can't tell that CPUs behave exactly > >>probabilistically --- it may > >>happen that one gets out of the wait loop always too > >>late. > > > >Well, I don't need them to be _exactly_ > >probabilistical. > > > >Anyway, if you have 2048 CPUs... you can perhaps get > >some non-broken > >ones. > > No intel document guarantees you that if more CPUs > simultaneously execute locked cmpxchg in a loop that a If we are talking 2048 cpus, we are talking ia64. > CPU will see compare success in a finite time. In fact, > CPUs can't guarantee this at all, because they don't > know that they're executing a spinlock --- for them its > just an instruction stream like anything else. ...even i386 has monitor/mwait these days. Pavel -- Thanks for all the (sleeping) penguins. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/