From: "M. Edward (Ed) Borasky" <znmeb@cesmail.net>
To: linux-btrace@vger.kernel.org
Subject: Re: [RFC] blktrace 2.0
Date: Wed, 28 Jan 2009 05:25:20 +0000 [thread overview]
Message-ID: <497FEC40.6090808@cesmail.net> (raw)
In-Reply-To: <497F844F.4010402@hp.com>
Alan D. Brunelle wrote:
[snip]
> I've down some testing on a small-ish machine - using valgrind to ensure
> proper handling of all memory, as well as a 16-way w/ >100 disks and
> things are working as expected. (At least blkrawverify, blkparse, btt,
> ... are all working fine for some test cases.)
I don't have anything that big to test it on, but I can certainly ask my
friends. :)
--
M. Edward (Ed) Borasky
I've never met a happy clam. In fact, most of them were pretty steamed.
next prev parent reply other threads:[~2009-01-28 5:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 22:01 [RFC] blktrace 2.0 Alan D. Brunelle
2009-01-28 5:25 ` M. Edward (Ed) Borasky [this message]
2009-01-29 10:59 ` Jens Axboe
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=497FEC40.6090808@cesmail.net \
--to=znmeb@cesmail.net \
--cc=linux-btrace@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.