qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Timothy Scott <tscott2@clemson.edu>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] PVFS2 Block Driver Support
Date: Thu, 27 Jun 2013 16:43:17 +0200	[thread overview]
Message-ID: <CAJSP0QXDRcDGPtxkVMQ2ddAtBa4bfwQ==H_u0X5zFymcwmwhBQ@mail.gmail.com> (raw)
In-Reply-To: <CA+4Zj15AdoNyocYc_Syp4d9TK81LzsetkPszSqaWrFHYUxNLMg@mail.gmail.com>

On Thu, Jun 27, 2013 at 4:25 PM, Timothy Scott <tscott2@clemson.edu> wrote:
> I am working on adding block driver support for PVFS2 that will allow images
> stored on PVFS2 systems to bypass the kernel module and hopefully improve
> performance significantly.

What performance bottlenecks are you seeing in the kernel which you
can bypass from QEMU userspace?

> Can you please advise on a couple of issues:
>   - Should qcow2 and other optimizing formats function when using pvfs2 as a
> transport/block layer?  ie 'qemu-img create -f qcow2 pvfs2:foo.img 10g'

qcow2 works on top of any "protocol" and it should work on top of
PVFS2.  QED does not and other formats may or may not (VHDX, VMDK,
etc).

>   - Are there any debugging tools or compile flags that are recommended for
> use in QEMU?  I am currently hacking around with gdb and having trouble
> navigating through much of the code.

You may find trace events useful, see docs/tracing.txt.

>   - Is there currently a testing suite/procedure for verifying new block
> drivers?

There is a test suite in tests/qemu-iotests/.  You will need to add
support for PVFS2, see how NBD and other protocols were added.

Stefan

  reply	other threads:[~2013-06-27 14:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 14:25 [Qemu-devel] PVFS2 Block Driver Support Timothy Scott
2013-06-27 14:43 ` Stefan Hajnoczi [this message]
2013-06-27 14:53   ` Stefan Hajnoczi
2013-06-27 21:40     ` Alex Bligh
2013-07-01  8:47       ` Stefan Hajnoczi
2013-07-03 15:41         ` Timothy Scott
2013-07-04  8:41           ` Stefan Hajnoczi
2013-07-08 14:54             ` Timothy Scott
2013-07-10 14:08             ` Timothy Scott
2013-07-10 14:31               ` Kevin Wolf

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='CAJSP0QXDRcDGPtxkVMQ2ddAtBa4bfwQ==H_u0X5zFymcwmwhBQ@mail.gmail.com' \
    --to=stefanha@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tscott2@clemson.edu \
    /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).