From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cuda.sgi.com (cuda2.sgi.com [192.48.176.25]) by oss.sgi.com (8.14.3/8.14.3/SuSE Linux 0.8) with ESMTP id o24AfaY9160072 for ; Thu, 4 Mar 2010 04:41:38 -0600 Date: Thu, 4 Mar 2010 05:43:04 -0500 From: Christoph Hellwig Subject: Re: using the scalable vmapi API again Message-ID: <20100304104304.GA10650@infradead.org> References: <20100215144807.GA9932@infradead.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20100215144807.GA9932@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: Alex Elder Cc: xfs@oss.sgi.com ping? On Mon, Feb 15, 2010 at 09:48:07AM -0500, Christoph Hellwig wrote: > Hi Alex, > > I've worked with Nick to make sure the regressions introduced by Nick's > scalable vmap API are fixed, so we an start using it again after we > had to disable it after a brief period in early 2009. > > Can you make sure commits d2859751cd0bf586941ffa7308635a293f943c17 and > 95f8e302c04c0b0c6de35ab399a5551605eeb006 get re-aplied to the XFS > tree, or maybe re-revert their revert commits > 3a011a171906a3a51a43bb860fb7c66a64cab140 and > cf7dab801796b9ee52a6dc99888a66bf476538ec. > > _______________________________________________ > xfs mailing list > xfs@oss.sgi.com > http://oss.sgi.com/mailman/listinfo/xfs ---end quoted text--- _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs