Re: [Qemu-devel] [PATCH v3 02/23] block: New BlockBackend

2014-09-21 Thread Markus Armbruster
Max Reitz writes: > On 16.09.2014 20:12, Markus Armbruster wrote: >> A block device consists of a frontend device model and a backend. >> >> A block backend has a tree of block drivers doing the actual work. >> The tree is managed by the block layer. >> >> We currently use a single abstraction Bl

Re: [Qemu-devel] [PATCH v3 02/23] block: New BlockBackend

2014-09-20 Thread Max Reitz
On 16.09.2014 20:12, Markus Armbruster wrote: A block device consists of a frontend device model and a backend. A block backend has a tree of block drivers doing the actual work. The tree is managed by the block layer. We currently use a single abstraction BlockDriverState both for tree nodes a

Re: [Qemu-devel] [PATCH v3 02/23] block: New BlockBackend

2014-09-19 Thread Markus Armbruster
Kevin Wolf writes: > Am 16.09.2014 um 20:12 hat Markus Armbruster geschrieben: >> A block device consists of a frontend device model and a backend. >> >> A block backend has a tree of block drivers doing the actual work. >> The tree is managed by the block layer. >> >> We currently use a single

Re: [Qemu-devel] [PATCH v3 02/23] block: New BlockBackend

2014-09-19 Thread Kevin Wolf
Am 16.09.2014 um 20:12 hat Markus Armbruster geschrieben: > A block device consists of a frontend device model and a backend. > > A block backend has a tree of block drivers doing the actual work. > The tree is managed by the block layer. > > We currently use a single abstraction BlockDriverState

[Qemu-devel] [PATCH v3 02/23] block: New BlockBackend

2014-09-16 Thread Markus Armbruster
A block device consists of a frontend device model and a backend. A block backend has a tree of block drivers doing the actual work. The tree is managed by the block layer. We currently use a single abstraction BlockDriverState both for tree nodes and the backend as a whole. Drawbacks: * Its AP