From: Andi Kleen <ak@suse.de>
To: Emmanuel Varagnat <Emmanuel_Varagnat-AEV010@email.mot.com>
Cc: Andi Kleen <ak@suse.de>, Hans Reiser <reiser@namesys.com>,
linux-kernel@vger.kernel.org
Subject: Re: Journal Filesystem Comparison on Netbench
Date: Tue, 28 Aug 2001 12:50:03 +0200 [thread overview]
Message-ID: <20010828125003.A27996@gruyere.muc.suse.de> (raw)
In-Reply-To: <3B8A6122.3C784F2D@us.ibm.com.suse.lists.linux.kernel> <3B8AA7B9.8EB836FF@namesys.com.suse.lists.linux.kernel> <oupsneck77v.fsf@pigdrop.muc.suse.de> <3B8B755F.D6317A9A@crm.mot.com>
In-Reply-To: <3B8B755F.D6317A9A@crm.mot.com>; from Emmanuel_Varagnat-AEV010@email.mot.com on Tue, Aug 28, 2001 at 12:41:35PM +0200
On Tue, Aug 28, 2001 at 12:41:35PM +0200, Emmanuel Varagnat wrote:
>
> Andi Kleen wrote:
> >
> > It does not really look like a locking problem. If you look at the profiling
> > logs it is pretty clear that the problem is the algorithm used in
> > bitmap.c:find_forward. find_forward and reiserfs_in_journal
> > ...
> > journaled blocks set also, to quickly skip them for the common case.
>
> I'm very interested in the way you did profiling.
> Did you compile the kernel with profiling options (gprof ?) ?
> If so, where the profiling information file is saved ?
I did not do any profiling in this case; I just read an existing log.
If you want to do profiling yourself you could use the simple
builtin statistical profiler: boot with profile=2 on the command line
and read the log at anytime using the readprofile command.
Other ways are documented on the lse homepage http://lse.sourceforge.net
-Andi
next prev parent reply other threads:[~2001-08-28 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3B8A6122.3C784F2D@us.ibm.com.suse.lists.linux.kernel>
[not found] ` <3B8AA7B9.8EB836FF@namesys.com.suse.lists.linux.kernel>
2001-08-28 6:51 ` Journal Filesystem Comparison on Netbench Andi Kleen
2001-08-28 10:41 ` Emmanuel Varagnat
2001-08-28 10:50 ` Andi Kleen [this message]
2001-08-28 11:35 ` Emmanuel Varagnat
2001-08-28 15:07 ` Andrew Theurer
2001-08-27 15:02 Andrew Theurer
2001-08-27 20:04 ` Hans Reiser
2001-08-27 20:29 ` Andrew Theurer
2001-08-27 21:19 ` Randy.Dunlap
2001-08-28 10:05 ` Roberto Nibali
2001-08-28 15:28 ` Andrew Theurer
2001-08-28 18:38 ` Andrew Morton
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=20010828125003.A27996@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=Emmanuel_Varagnat-AEV010@email.mot.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
/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;
as well as URLs for NNTP newsgroup(s).