From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 15 May 2008 03:13:57 +0200 From: Nick Piggin Subject: Re: [patch 2/2]: introduce fast_gup Message-ID: <20080515011357.GF30448@wotan.suse.de> References: <20080328025455.GA8083@wotan.suse.de> <20080328030023.GC8083@wotan.suse.de> <1208857356.7115.218.camel@twins> <20080422094629.GC23770@wotan.suse.de> <1210789994.6377.21.camel@norville.austin.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1210789994.6377.21.camel@norville.austin.ibm.com> Sender: owner-linux-mm@kvack.org Return-Path: To: Dave Kleikamp Cc: Peter Zijlstra , Andrew Morton , axboe@kernel.dk, linux-mm@kvack.org, linux-arch@vger.kernel.org, torvalds@linux-foundation.org List-ID: On Wed, May 14, 2008 at 01:33:14PM -0500, Dave Kleikamp wrote: > > Ah good catch. As you can see I haven't done any highmem testing ;) > > Which I will do so before sending upstream. > > Which will be when? We'd really like to see this in mainline as soon as > possible and in -mm in the meanwhile. Well I just got all the "hard" core mm stuff past Linus in this merge window, and got a couple of preexisting memory ordering bugs fixed.. So I am planning to get it into -mm, ready for the next merge window. I'm a little concerned about Peter's instability reports, but maybe they're just an -rt thing. But I don't think we've found any holes in fast_gup yet (although I think I need to add one last check to ensure it won't pick up kernel addresses). Thanks, Nick -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org