From: "Stephen C. Tweedie" <sct@redhat.com>
To: Shawn Starr <spstarr@sh0n.net>
Cc: sct@redhat.com, akpm@digeo.com, Con Kolivas <conman@kolivas.net>,
linux-kernel@vger.kernel.org
Subject: Re: [BENCHMARK] EXT2 vs EXT3 System calls via oprofile using contest 0.34
Date: Mon, 23 Sep 2002 22:34:29 +0100 [thread overview]
Message-ID: <20020923223429.V11682@redhat.com> (raw)
In-Reply-To: <200209190142.58122.spstarr@sh0n.net>; from spstarr@sh0n.net on Thu, Sep 19, 2002 at 01:42:58AM -0400
Hi,
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
do_get_write_access.
> 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.
--Stephen
next prev parent reply other threads:[~2002-09-23 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-19 5:42 [BENCHMARK] EXT2 vs EXT3 System calls via oprofile using contest 0.34 Shawn Starr
2002-09-23 21:34 ` Stephen C. Tweedie [this message]
2002-09-24 0:06 ` Michael Cohen
2002-09-24 0:11 ` Shawn Starr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020923223429.V11682@redhat.com \
--to=sct@redhat.com \
--cc=akpm@digeo.com \
--cc=conman@kolivas.net \
--cc=linux-kernel@vger.kernel.org \
--cc=spstarr@sh0n.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox