using the scalable vmapi API again

xfs

using the scalable vmapi API again

To:	Alex Elder <aelder@xxxxxxx>
Subject:	using the scalable vmapi API again
From:	Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:	Mon, 15 Feb 2010 09:48:07 -0500
Cc:	xfs@xxxxxxxxxxx
User-agent:	Mutt/1.5.19 (2009-01-05)

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.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
using the scalable vmapi API again, Christoph Hellwig <=

Previous by Date:	[PATCH 1/4] [PATCH 1/4] xfs: merge xfs_lrw.c into xfs_file.c, Christoph Hellwig
Next by Date:	Re: [PATCH 0/4] implement optimized fdatasync, Andi Kleen
Previous by Thread:	[PATCH 0/4] implement optimized fdatasync, Christoph Hellwig
Next by Thread:	[PATCH] xfs: fix xfs_fsblock_t tracing, Christoph Hellwig
Indexes:	[Date] [Thread] [Top] [All Lists]