From: Nick Piggin Subject: Re: [PATCH 2/4] CacheFiles: Revert the addition of write_one_page() Date: Sat, 4 Apr 2009 16:55:42 +1100 Message-ID: <200904041655.43360.nickpiggin@yahoo.com.au> References: <20090403135007.GB31907@infradead.org> <20090403094143.9510.80474.stgit@warthog.procyon.org.uk> <10983.1238766809@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: Christoph Hellwig , linux-fsdevel@vger.kernel.org, nfsv4@linux-nfs.org, linux-kernel@vger.kernel.org To: David Howells Return-path: In-Reply-To: <10983.1238766809@redhat.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfsv4-bounces@linux-nfs.org Errors-To: nfsv4-bounces@linux-nfs.org List-Id: linux-fsdevel.vger.kernel.org On Saturday 04 April 2009 00:53:29 David Howells wrote: > Christoph Hellwig wrote: > > > Note that in the patch series going into mainline eventually this should > > not be a separate patch but the new ops should never be introduced. > > Yes, probably, but this makes it easier for people to see what I'm proposing > to change. Definitely yes please. kmap resources are not infinite but there is obviously a proper kmap allocator so long as you only kmap one page at a time, then others will just block waiting for more. On sane platforms of course there is no penalty at all. So this change is definitely required if you want to get this patchset in. The alternative is to come up with a new API and get that merged first, but I figure you don't want that kind of dependency.