From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932149AbYETLF7 (ORCPT ); Tue, 20 May 2008 07:05:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1765760AbYETLFe (ORCPT ); Tue, 20 May 2008 07:05:34 -0400 Received: from relay2.sgi.com ([192.48.171.30]:34986 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1765731AbYETLFd (ORCPT ); Tue, 20 May 2008 07:05:33 -0400 Date: Tue, 20 May 2008 06:05:29 -0500 From: Robin Holt To: Nick Piggin Cc: Robin Holt , Christoph Lameter , Nick Piggin , Linus Torvalds , Andrea Arcangeli , Andrew Morton , Jack Steiner , Peter Zijlstra , kvm-devel@lists.sourceforge.net, Kanoj Sarcar , Roland Dreier , Steve Wise , linux-kernel@vger.kernel.org, Avi Kivity , linux-mm@kvack.org, general@lists.openfabrics.org, Hugh Dickins , Rusty Russell , Anthony Liguori , Chris Wright , Marcelo Tosatti , Eric Dumazet , "Paul E. McKenney" Subject: Re: [PATCH 08 of 11] anon-vma-rwsem Message-ID: <20080520110528.GD30341@sgi.com> References: <20080514041122.GE24516@wotan.suse.de> <20080514112625.GY9878@sgi.com> <20080515075747.GA7177@wotan.suse.de> <20080515235203.GB25305@wotan.suse.de> <20080516112306.GA4287@sgi.com> <20080516115005.GC4287@sgi.com> <20080520053145.GA19502@wotan.suse.de> <20080520100111.GC30341@sgi.com> <20080520105025.GA25791@wotan.suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080520105025.GA25791@wotan.suse.de> User-Agent: Mutt/1.5.17+20080114 (2008-01-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 20, 2008 at 12:50:25PM +0200, Nick Piggin wrote: > On Tue, May 20, 2008 at 05:01:11AM -0500, Robin Holt wrote: > > On Tue, May 20, 2008 at 07:31:46AM +0200, Nick Piggin wrote: > > > > > > Really? You can get the information through via a sleeping messaging API, > > > but not a non-sleeping one? What is the difference from the hardware POV? > > > > That was covered in the early very long discussion about 28 seconds. > > The read timeout for the BTE is 28 seconds and it automatically retried > > for certain failures. In interrupt context, that is 56 seconds without > > any subsequent interrupts of that or lower priority. > > I thought you said it would be possible to get the required invalidate > information without using the BTE. Couldn't you use XPMEM pages in > the kernel to read the data out of, if nothing else? I was wrong about that. I thought it was safe to do an uncached write, but it turns out any processor write is uncontained and the MCA that surfaces would be fatal. Likewise for the uncached read.