qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] stacking the block layer
Date: Wed, 12 Aug 2009 14:43:44 +0200	[thread overview]
Message-ID: <4A82B900.4070605@redhat.com> (raw)
In-Reply-To: <B08B5C37-2804-4F24-9015-505D8A050D57@suse.de>

Alexander Graf schrieb:
> Hi list,
> 
> I just implemented dzip (seekable gzip) support and stumbled across a  
> major bummer in the block layer:
> 
> Formats can't be stacked.
> 
> So why do we have this restriction? From what I could tell, the  
> current code would just run into an endless loop, because the probe  
> function of the format we're trying to open triggers when trying to  
> open the underlying file.
> 
> Now that is a valid problem, but can't we just match that when opening  
> a file from say "qcow2" that we simply don't open backing files as  
> "qcow2" as well?
> 
> That way we could have qcow2 in dzip served via HTTP. At the end of  
> the day I also want to bring tar into the game, so we'd have qcow2  
> (format) in tar (format) in dzip (format) on HTTP (protocol).

No, this should actually be qcow2 (format) on tar (protocol) on dzip
(protocol) on http (protocol). I'm not sure though if you can specify
things like tar:dzip:http://... with the current block code but I don't
think you would run into the problem you described above with protocols.

Kevin

      reply	other threads:[~2009-08-12 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-05  1:37 [Qemu-devel] stacking the block layer Alexander Graf
2009-08-12 12:43 ` Kevin Wolf [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=4A82B900.4070605@redhat.com \
    --to=kwolf@redhat.com \
    --cc=agraf@suse.de \
    --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).