[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m3ipmspaug.fsf@blackfin.pond.sub.org>
Date: Thu, 10 Nov 2011 10:48:07 +0100
From: Markus Armbruster <armbru@...hat.com>
To: Sasha Levin <levinsasha928@...il.com>
Cc: Pekka Enberg <penberg@...nel.org>,
Anthony Liguori <anthony@...emonkey.ws>,
Pekka Enberg <penberg@...helsinki.fi>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Avi Kivity <avi@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, Christoph Hellwig <hch@....de>
Subject: Re: [RFC/GIT PULL] Linux KVM tool for v3.2
Sasha Levin <levinsasha928@...il.com> writes:
> On Thu, Nov 10, 2011 at 10:57 AM, Markus Armbruster <armbru@...hat.com> wrote:
>> Sasha Levin <levinsasha928@...il.com> writes:
[...]
>>> I'm actually not sure why KVM tool got QCOW support in the first
>>> place. You can have anything QCOW provides if you use btrfs (among
>>> several other FSs).
>>
>> Maybe it's just me, but isn't it weird to have a filesystem (QCOW2)
>> sitting in the kernel sources that you can't mount(2)?
>>
>
> It's not really a filesystem, it's a disk image :)
Sloppy language on my part, sorry about that.
It's a transport for blocks. We have a few of those in the kernel
already: block devices. Including loop devices and DRBD. You use a
filesystem to interpret their contents. The resulting stack is what
gets mounted. Adding another transport for blocks to the kernel that
cannot be used that way strikes me as weird.
[...]
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists