From: "Alan D. Brunelle" <Alan.Brunelle@hp.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][v3] blktrace: conversion to tracepoints
Date: Fri, 07 Nov 2008 09:29:56 -0500 [thread overview]
Message-ID: <491450E4.2080802@hp.com> (raw)
In-Reply-To: <20081030073134.GM31673@kernel.dk>
>
> I'll apply this for 2.6.29. I'm assuming you have tested this as well?
>
FYI: I tested this on a 16-way AMD x86_64 box (128GB RAM, a couple of
Smart Array (CCISS) P800's). Running Jens' for-2.6.29 git tree versus a
recent Linus 2.6.28-rc3 tree. I was doing kernel makes (10 passes for
both kernels), and found that things worked just fine. All values below
are in seconds:
2.6.28-rc3:
Part Min Avg Max Dev
-------- ------- ------- ------- -------
untar 17.996 22.565 23.522 1.690
mk-cfg 3.279 3.454 3.529 0.070
mk-kern 140.837 141.557 142.549 0.626
mk-clean 10.460 11.604 12.710 0.758
-------- ------- ------- ------- -------
Combd 172.941 179.180 181.600 2.470
======== ======= ======= ======= =======
%sys 7.67% 7.78% 8.03% 0.114
Jens' origin/for-2.6.29:
Part Min Avg Max Dev
-------- ------- ------- ------- -------
untar 18.138 22.576 24.279 1.693
mk-cfg 3.270 3.483 3.751 0.118
mk-kern 141.290 142.115 142.666 0.439
mk-clean 8.263 9.609 10.211 0.624
-------- ------- ------- ------- -------
Combd 173.736 177.783 179.654 1.786
======== ======= ======= ======= =======
%sys 7.77% 7.85% 8.01% 0.074
Not sure why the 'make clean' portion of the runs went noticeably better
with the newer code, but in any event, I don't see much difference
elsewhere, and for sure the blktrace portion of things worked correctly.
[blktrace + blkparse + blkrawverify + btt all worked just fine out of
the box.]
Regards,
Alan
next prev parent reply other threads:[~2008-11-07 14:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 12:05 [PATCH][v2] blktrace: conversion to tracepoints Arnaldo Carvalho de Melo
2008-10-29 13:18 ` Jens Axboe
2008-10-29 15:50 ` Arnaldo Carvalho de Melo
2008-10-29 19:43 ` [PATCH][v3] " Arnaldo Carvalho de Melo
2008-10-30 7:31 ` Jens Axboe
2008-10-30 11:03 ` Arnaldo Carvalho de Melo
2008-10-30 11:11 ` Jens Axboe
2008-11-03 17:21 ` Arnaldo Carvalho de Melo
2008-11-03 17:22 ` Jens Axboe
2008-11-03 18:08 ` Arnaldo Carvalho de Melo
2008-11-07 14:29 ` Alan D. Brunelle [this message]
2008-11-07 14:32 ` Jens Axboe
2008-11-07 15:38 ` Arnaldo Carvalho de Melo
2008-10-30 14:44 ` [PATCH][v3] blktrace: conversion to tracepoints 2.6.27.4 backport Mathieu Desnoyers
2008-10-30 14:47 ` Arnaldo Carvalho de Melo
2008-10-29 15:17 ` [PATCH][v2] blktrace: conversion to tracepoints Mathieu Desnoyers
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=491450E4.2080802@hp.com \
--to=alan.brunelle@hp.com \
--cc=acme@redhat.com \
--cc=compudj@krystal.dyndns.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.