Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264732AbTIDGnp (ORCPT ); Thu, 4 Sep 2003 02:43:45 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264737AbTIDGnp (ORCPT ); Thu, 4 Sep 2003 02:43:45 -0400 Received: from x35.xmailserver.org ([208.129.208.51]:36482 "EHLO x35.xmailserver.org") by vger.kernel.org with ESMTP id S264732AbTIDGno (ORCPT ); Thu, 4 Sep 2003 02:43:44 -0400 X-AuthUser: davidel@xmailserver.org Date: Wed, 3 Sep 2003 23:38:07 -0700 (PDT) From: Davide Libenzi X-X-Sender: davide@bigblue.dev.mdolabs.com To: Nagendra Singh Tomar cc: Jamie Lokier , Geert Uytterhoeven , Roman Zippel , Kars de Jong , Linux/m68k kernel mailing list , Linux Kernel Development Subject: Re: x86, ARM, PARISC, PPC, MIPS and Sparc folks please run this In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 746 Lines: 20 On Wed, 3 Sep 2003, Nagendra Singh Tomar wrote: > I meant to ask if the store buffer is snooped by *other CPUs*. To maintain > self coherence the local store buffer has to be anyway consulted by local > loads to give the latest stored value. There are CPUs (at least some version of Alpha, 21064 IIRC) that uses flush upon L1 read miss, so they do not snoop their local WB. IIRC P5 has internal and external snooping while P6, using a write allocate L1, does not have external snooping. - Davide - 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/