From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id o0R8bKHF180457 for ; Wed, 27 Jan 2010 02:37:21 -0600 Received: from mx1.suse.de (localhost [127.0.0.1]) by cuda.sgi.com (Spam Firewall) with ESMTP id 4F3AAF5D90C for ; Wed, 27 Jan 2010 00:38:24 -0800 (PST) Received: from mx1.suse.de (cantor.suse.de [195.135.220.2]) by cuda.sgi.com with ESMTP id pfv6n6EmPn4CVr6B for ; Wed, 27 Jan 2010 00:38:24 -0800 (PST) Date: Wed, 27 Jan 2010 19:38:19 +1100 From: Nick Piggin Subject: Re: [patch 2/2] xfs: use scalable vmap API Message-ID: <20100127083819.GA11072@laptop> References: <20081021082542.GA6974@wotan.suse.de> <20081021082735.GB6974@wotan.suse.de> <20081021120932.GB13348@infradead.org> <20081022093018.GD4359@wotan.suse.de> <20100119121505.GA9428@infradead.org> <20100125075445.GD19664@laptop> <20100125081750.GA20012@infradead.org> <20100125083309.GF19664@laptop> <20100125123746.GA24406@laptop> <20100125213403.GA1309@infradead.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20100125213403.GA1309@infradead.org> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: xfs-bounces@oss.sgi.com Errors-To: xfs-bounces@oss.sgi.com To: Christoph Hellwig Cc: linux-mm@kvack.org, xfs@oss.sgi.com On Mon, Jan 25, 2010 at 04:34:03PM -0500, Christoph Hellwig wrote: > On Mon, Jan 25, 2010 at 11:37:46PM +1100, Nick Piggin wrote: > > On Mon, Jan 25, 2010 at 07:33:09PM +1100, Nick Piggin wrote: > > > > Any easy way to get them? Sorry, not uptodate on your new vmalloc > > > > implementation anymore. > > > > > > Let me try writing a few (tested) patches here first that I can send you. > > > > Well is it easy to reproduce the vmap failure? Here is a better tested > > patch if you can try it. It fixes a couple of bugs and does some purging > > of fragmented blocks. > > So far I've not run out of vmalloc space yet with quite a few xfstests > iterations and not encountered any other problems either. > > Thanks for looking into this! OK thanks for testing. I'll send it upstream if you haven't had any problems so far. _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs