From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-io - an I/O path exerciser
Date: Sun, 05 Apr 2009 13:44:08 -0500 [thread overview]
Message-ID: <49D8FBF8.2080301@us.ibm.com> (raw)
In-Reply-To: <20090329084953.GA13311@lst.de>
Christoph Hellwig wrote:
> This patch adds a new qemu-io tool that links against the block layer and
> image formats and allow to exercise them without needing a guest image.
> It is inspired by the xfs_io tool which does the same for plain file I/O.
> In fact the libxcmd library which is the backend of xfs_io is reused by this
> tool in a limited fashing (cmd.[ch] files).
>
> This version tests out most of the plain block I/O commands with the
> most notable absent commands beeing snapshot handling and real aio.
>
> This tool is the basis of the I/O path test suite I'm working on right now.
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
>
Applied. Thanks.
--
Regards,
Anthony Liguori
prev parent reply other threads:[~2009-04-05 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 8:49 [Qemu-devel] [PATCH] qemu-io - an I/O path exerciser Christoph Hellwig
2009-04-05 18:44 ` Anthony Liguori [this message]
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=49D8FBF8.2080301@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.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 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).