From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail138.messagelabs.com (mail138.messagelabs.com [216.82.249.35]) by kanga.kvack.org (Postfix) with ESMTP id 40D556B0047 for ; Mon, 25 Jan 2010 07:39:47 -0500 (EST) Date: Mon, 25 Jan 2010 07:39:44 -0500 From: Christoph Hellwig Subject: Re: [patch 2/2] xfs: use scalable vmap API Message-ID: <20100125123943.GA7394@infradead.org> 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100125123746.GA24406@laptop> Sender: owner-linux-mm@kvack.org To: Nick Piggin Cc: Christoph Hellwig , xfs@oss.sgi.com, linux-mm@kvack.org List-ID: 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. > > If it does not help, can you tell me how many CPUs in your system? The simplest one to reproduce it is a 1 cpu kvm virtual machine. Will give your patch a try ASAP - while it's easy to reproduce it takes some time as I appears only when doing a second xfstests run after a first finished fine, which makes it look like a leak to me. -- 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