From: Chris Mason <mason@suse.com>
To: Magnus Damm <magnus.damm@gmail.com>
Subject: Re: Mercurial 0.3 vs git benchmarks
Date: Tue, 26 Apr 2005 14:18:18 -0400
User-Agent: KMail/1.8
Cc: Linus Torvalds <torvalds@osdl.org>, Mike Taht <mike.taht@timesys.com>,
       Matt Mackall <mpm@selenic.com>,
       linux-kernel <linux-kernel@vger.kernel.org>, git@vger.kernel.org
References: <20050426004111.GI21897@waste.org> <200504261138.46339.mason@suse.com> <aec7e5c305042609231a5d3f0@mail.gmail.com>
In-Reply-To: <aec7e5c305042609231a5d3f0@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200504261418.18825.mason@suse.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1202
Lines: 26

On Tuesday 26 April 2005 12:23, Magnus Damm wrote:

> Well, maybe I misunderstood everything, but I thought you were
> applying a lot of patches and complained that it took a lot of time
> due to the data order.
>
> When I applied a lot of patches to the kernel recently the cpu load
> dropped to zero after a while and the HD worked hard a sec or two and
> then things came back again. My primitive guess is that it was because
> the ext3 journal became full. To workaround this fact I started
> hacking on this in-memory patcher.

It looks like you'll only see the commits on ext3 when the log fills, and on 
reiser3 you'll see it every 5 seconds or when the log fills.  With the 
default mount options, both ext3 and reiser will flush the data blocks at the 
same time they are writing the metadata.

The easiest way to get around this is to mount -o data=writeback on 
ext3/reiser, but you'll still have to wait for the data blocks eventually.  

-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/