qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Alberto Garcia <berto@igalia.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/3] block: Support streaming to an intermediate layer
Date: Thu, 5 Mar 2015 16:15:52 +0100	[thread overview]
Message-ID: <20150305151552.GF5427@noname.redhat.com> (raw)
In-Reply-To: <20150305145831.GA750@igalia.com>

Am 05.03.2015 um 15:58 hat Alberto Garcia geschrieben:
> On Thu, Mar 05, 2015 at 03:04:25PM +0100, Kevin Wolf wrote:
> 
> > The bs parameter is now only used for the following things:
> > 
> > 1. As the default for top
> 
> Right.
> 
> > 2. For error handling: Any errors are reported for bs, even though
> >    they are actually for top. Is this correct behaviour? It looks
> >    questionable to me.
> 
> Hmm... I guess you mean when calling block_job_error_action(), I
> probably overlooked that.

Yes, that and the check whether iostatus is enabled.

> > 3. As the BDS that owns the job
> > 
> > My question is whether we can't simply call stream_start() with an
> > intermediate node as bs instead of introducing a new parameter. I'm
> > not completely sure about the consequences of 3., i.e. moving
> > ownership of a block job to some BDS somewhere down the chain, but
> > otherwise it should be possible and seems cleaner.
> 
> We can, that was actually the first thing I tried and it does work,
> but then I noticed that other parts of the code would need changes,
> e.g. qmp_query_block_jobs() must be modified to iterate over all nodes
> of each device.
> 
> Since I was also not sure about the consequences of such a change I
> opted for the conservative approach.

I see. I'm worried about the external API. If we let the root node own
the job, we may paint ourselves into a corner with respect to nodes with
multiple users and therefore multiple possible root nodes.

Kevin

  reply	other threads:[~2015-03-05 15:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-20 13:53 [Qemu-devel] [PATCH 0/3] Support streaming to an intermediate layer Alberto Garcia
2015-02-20 13:53 ` [Qemu-devel] [PATCH 1/3] block: " Alberto Garcia
2015-03-05 14:04   ` Kevin Wolf
2015-03-05 14:58     ` Alberto Garcia
2015-03-05 15:15       ` Kevin Wolf [this message]
2015-03-05 15:47         ` Alberto Garcia
2015-03-12 13:18     ` Alberto Garcia
2015-02-20 13:53 ` [Qemu-devel] [PATCH 2/3] block: Add QMP support for " Alberto Garcia
2015-02-20 22:38   ` Eric Blake
2015-02-23 12:23     ` Alberto Garcia
2015-02-23 13:04       ` Kevin Wolf
2015-02-24 14:08         ` Markus Armbruster
2015-03-05 14:09   ` Kevin Wolf
2015-03-05 15:12     ` Alberto Garcia
2015-03-11 16:38     ` Alberto Garcia
2015-03-12 15:45       ` Kevin Wolf
2015-03-17 15:00         ` Alberto Garcia
2015-03-17 15:22           ` Eric Blake
2015-03-17 15:40             ` Alberto Garcia
2015-03-17 15:28           ` Kevin Wolf
2015-03-18 12:29         ` Alberto Garcia
2015-02-20 13:53 ` [Qemu-devel] [PATCH 3/3] docs: Document how to stream " Alberto Garcia
2015-02-20 17:34 ` [Qemu-devel] [PATCH 0/3] Support streaming " Eric Blake
2015-02-20 19:05   ` Alberto Garcia
2015-02-20 22:49     ` Eric Blake
2015-02-22 15:08       ` Alberto Garcia

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=20150305151552.GF5427@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=berto@igalia.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).