qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: OHMURA Kei <ohmura.kei@lab.ntt.co.jp>
To: Juan Quintela <quintela@redhat.com>
Cc: ohmura.kei@lab.ntt.co.jp,
	Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Avi Kivity <avi@redhat.com>
Subject: [Qemu-devel] Re: virtio_blk_load() question
Date: Fri, 19 Mar 2010 11:53:48 +0900	[thread overview]
Message-ID: <4BA2E73C.1080405@lab.ntt.co.jp> (raw)
In-Reply-To: <m3eijhomsy.fsf@trasno.mitica>

On 2010/03/18 21:07, Juan Quintela wrote:
> Really, ordering doesn't matter (in this case):
> 
> see virtio-blk.c:virtio_blk_dma_restart_bh()
> 
>     QLIST_FOREACH_SAFE(req, &rq_copy, next, next_req) {
>         QLIST_REMOVE(req, next);
>         virtio_blk_handle_request(req, &mrb);
>     }
> 
> This mean that we are just removing from the beggining and addin from
> the beginnig (i.e. reversing).  Adding by the beggining made it easier,
> but I can change if you mean.

Thanks, I understood.
However, since it's difficult to understand this at first glance,
it would be great if you could modify, but I'm OK if you could just add
comments on this to the exiting patch.  It's kind for a newbie like me.


> Notice that except if there are any errors (I was not able to trigger
> it, but didnt' try too hard), that list is going to be syncked in the 
> 
>         qemu_aio_flush();
>         bdrv_flush_all();
> 
> in migrate_fd_put_ready(), so it is not trivial to hit it and probably
> the difference is just theoretical.

Thank you for your information.

      reply	other threads:[~2010-03-19  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  4:30 [Qemu-devel] virtio_blk_load() question OHMURA Kei
2010-03-18  7:37 ` [Qemu-devel] " Juan Quintela
2010-03-18  9:42   ` OHMURA Kei
2010-03-18 12:07     ` Juan Quintela
2010-03-19  2:53       ` OHMURA Kei [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=4BA2E73C.1080405@lab.ntt.co.jp \
    --to=ohmura.kei@lab.ntt.co.jp \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=tamura.yoshiaki@lab.ntt.co.jp \
    /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).