Re: [BENCHMARK] EXT2 vs EXT3 System calls via oprofile using contest 0.34

From: Stephen C. Tweedie (
Date: Mon Sep 23 2002 - 16:34:29 EST


On Thu, Sep 19, 2002 at 01:42:58AM -0400, Shawn Starr wrote:
> EXT3 kernel calls
> ==========
> Top 3:
> c013cf70 16380 4.51113 get_hash_table /lib/modules/2.4.20-pre7-rmap14a-xfs-uml-shawn12d/build/vmlinux

Same as ext2...

> c016b090 22883 6.30209 do_get_write_access /lib/modules/2.4.20-pre7-rmap14a-xfs-uml-shawn12d/build/vmlinux

That's an inevitable penalty from the way ext3 does journaling --- you
get two copies of data if a filesystem operation updates a block that
is still being journaled (because we need to snapshot the old copy to
write to the journal). That's done when ext3 notifies an intent to
modify the old block, so all those copies show up in

> c0164910 26375 7.2638 ext3_do_update_inode /lib/modules/2.4.20-pre7-rmap14a-xfs-uml-shawn12d/build/vmlinux

I've got a fix for excessive CPU time spent here.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Mon Sep 23 2002 - 22:00:40 EST