From mboxrd@z Thu Jan 1 00:00:00 1970 From: Trond Myklebust Subject: Re: [PATCH RFC] extent mapped page cache Date: Tue, 24 Jul 2007 16:13:05 -0400 Message-ID: <1185307985.6586.50.camel@localhost> References: <20070710210326.GA29963@think.oraclecorp.com> <20070724160032.7a7097db@think.oraclecorp.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Nick Piggin , Linux Kernel Mailing List , Linux Memory Management List , linux-fsdevel@vger.kernel.org To: Chris Mason Return-path: Received: from pat.uio.no ([129.240.10.15]:52175 "EHLO pat.uio.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751807AbXGXUNL (ORCPT ); Tue, 24 Jul 2007 16:13:11 -0400 In-Reply-To: <20070724160032.7a7097db@think.oraclecorp.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, 2007-07-24 at 16:00 -0400, Chris Mason wrote: > On Tue, 10 Jul 2007 17:03:26 -0400 > Chris Mason wrote: > > > This patch aims to demonstrate one way to replace buffer heads with a > > few extent trees. Buffer heads provide a few different features: > > > > 1) Mapping of logical file offset to blocks on disk > > 2) Recording state (dirty, locked etc) > > 3) Providing a mechanism to access sub-page sized blocks. > > > > This patch covers #1 and #2, I'll start on #3 a little later next > > week. > > > Well, almost. I decided to try out an rbtree instead of the radix, > which turned out to be much faster. Even though individual operations > are slower, the rbtree was able to do many fewer ops to accomplish the > same thing, especially for merging extents together. It also uses much > less ram. The problem with an rbtree is that you can't use it together with RCU to do lockless lookups. You can probably modify it to allocate nodes dynamically (like the radix tree does) and thus make it RCU-compatible, but then you risk losing the two main benefits that you list above. Trond