All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] dmg: fix ->open failure
Date: Mon, 11 Jan 2010 18:47:23 +0100	[thread overview]
Message-ID: <20100111174723.GA7204@lst.de> (raw)
In-Reply-To: <4B4B31A8.6010405@redhat.com>

On Mon, Jan 11, 2010 at 03:11:52PM +0100, Kevin Wolf wrote:
> More or less the same hack, just in cleaner? Or trying to fundamentally
> change things? I think you haven't answered yet to what I said in the
> thread of my original hack. I'm quoting it here for convenience:

Well, not dealing with the format list in raw, but rather in block.c

> > Ok, if you start talking about layering, we can have a fundamental
> > discussion on this topic and why the layering is broken anyway.
> > Logically, we have image formats like qcow2, VMDK and raw, and they are
> > stored in files, on CD-ROMs or general block devices. From a layering
> > perspective, it is wrong to include the latter in the raw format driver
> > in the first place.
> 
> Actually, I think the differentiation between raw files and host_* is at
> the same level as protocols are. Probably they should be implemented
> very similarly.
> 
> Do you think it's possible/worth the effort to try putting things
> straight here?

So what you want is basically:

 - hdev_* and file as protocols in addition to nbd/ftp/http/..
 - a raw image format that can be used ontop of any protocol instead of
   an image format

That would indeed be a much better, not to say actually logical
layering.  The raw image format would be more or less a no-op just
stacking ontop of the protocol.  If we can find a way to implement this
efficiently it might be the way to go.

  reply	other threads:[~2010-01-11 17:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 13:06 [Qemu-devel] [PATCH] dmg: fix ->open failure Christoph Hellwig
2010-01-11 13:43 ` Kevin Wolf
2010-01-11 13:46   ` Christoph Hellwig
2010-01-11 13:56     ` Kevin Wolf
2010-01-11 14:00       ` Christoph Hellwig
2010-01-11 14:11         ` Kevin Wolf
2010-01-11 17:47           ` Christoph Hellwig [this message]
2010-01-12  9:25             ` Kevin Wolf
2010-01-11 19:07         ` malc
2010-01-11 19:51 ` Anthony Liguori

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=20100111174723.GA7204@lst.de \
    --to=hch@lst.de \
    --cc=kwolf@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.