Andi Kleen wrote:
>
> 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
The profiles I provided were with SGI's kernprof 0.9.2. I chose ACG,
which does have a lot of overhead (cg_record_arc and mcount), but also
provides a lot of information. I have a separate kernel for each
filesystem and each filesystem+profle_patch (10 kernels). No modules
were used so that all profiles have no 'unknown kernel' functions. Each
profile was taken for 60 seconds, starting at 90 seconds into the test.
All profiles were taken on the 44 client test.
Andrew Theurer
-
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/
This archive was generated by hypermail 2b29 : Fri Aug 31 2001 - 21:00:29 EST