Stefan,
--On 24 June 2013 11:31:35 +0200 Stefan Hajnoczi wrote:
It sounds like the cache is in the sheep daemon and therefore has a
global view of all volumes being accessed from this host. That way it
can do things like share the cached snapshot data between volumes.
Yes, that's potentiall
On Fri, Jun 21, 2013 at 11:18:07PM +0800, Liu Yuan wrote:
> On 06/20/2013 11:58 PM, Sage Weil wrote:
> > On Thu, 20 Jun 2013, Stefan Hajnoczi wrote:
> >>> The concrete problem here is that flashcache/dm-cache/bcache don't
> >>> work with the rbd (librbd) driver, as flashcache/dm-cache/bcache
> >>>
On Fri, 21 Jun 2013, Stefan Hajnoczi wrote:
> >> but if there's really a case for it with performance profiles then I
> >> guess it would be necessary. But we should definitely get feedback from
> >> the Ceph folks too.
> >
> >
> > The specific problem we are trying to solve (in case that's not
>
On Fri, 21 Jun 2013, Alex Bligh wrote:
> Sage,
>
> --On 20 June 2013 08:58:19 -0700 Sage Weil wrote:
>
> > > I'd like to hear from Ceph folks what their position on kernel rbd vs
> > > librados is. Why one do they recommend for QEMU guests and what are the
> > > pros/cons?
> >
> > I agree that
On 06/20/2013 11:58 PM, Sage Weil wrote:
> On Thu, 20 Jun 2013, Stefan Hajnoczi wrote:
>>> The concrete problem here is that flashcache/dm-cache/bcache don't
>>> work with the rbd (librbd) driver, as flashcache/dm-cache/bcache
>>> cache access to block devices (in the host layer), and with rbd
>>>
Stefan,
--On 21 June 2013 14:55:20 +0200 Stefan Hajnoczi wrote:
I understand the limitations with kernel block devices - their
setup/teardown is an extra step outside QEMU and privileges need to be
managed. That basically means you need to use a management tool like
libvirt to make it usable.
On Thu, Jun 20, 2013 at 5:58 PM, Sage Weil wrote:
> On Thu, 20 Jun 2013, Stefan Hajnoczi wrote:
> I'm not really sure what the best path forward is. Putting the
> functionality in qemu would benefit lots of other storage backends,
> putting it in librbd would capture various other librbd users (x
On Thu, Jun 20, 2013 at 4:25 PM, Alex Bligh wrote:
> Stefan,
>
>
> --On 20 June 2013 11:46:18 +0200 Stefan Hajnoczi wrote:
>
>>> The concrete problem here is that flashcache/dm-cache/bcache don't
>>> work with the rbd (librbd) driver, as flashcache/dm-cache/bcache
>>> cache access to block device
Sage,
--On 20 June 2013 08:58:19 -0700 Sage Weil wrote:
I'd like to hear from Ceph folks what their position on kernel rbd vs
librados is. Why one do they recommend for QEMU guests and what are the
pros/cons?
I agree that a flashcache/bcache-like persistent cache would be a big win
for qemu
On Thu, 20 Jun 2013, Stefan Hajnoczi wrote:
> > The concrete problem here is that flashcache/dm-cache/bcache don't
> > work with the rbd (librbd) driver, as flashcache/dm-cache/bcache
> > cache access to block devices (in the host layer), and with rbd
> > (for instance) there is no access to a bloc
Stefan,
--On 20 June 2013 11:46:18 +0200 Stefan Hajnoczi wrote:
The concrete problem here is that flashcache/dm-cache/bcache don't
work with the rbd (librbd) driver, as flashcache/dm-cache/bcache
cache access to block devices (in the host layer), and with rbd
(for instance) there is no access
On Wed, Jun 19, 2013 at 10:28:53PM +0100, Alex Bligh wrote:
> --On 11 April 2013 11:25:48 +0200 Stefan Hajnoczi
> wrote:
>
> >>I'd like to experiment with adding persistent writeback cache to qemu.
> >>The use case here is where non-local storage is used (e.g. rbd, ceph)
> >>using the qemu driver
Stefan,
--On 11 April 2013 11:25:48 +0200 Stefan Hajnoczi
wrote:
I'd like to experiment with adding persistent writeback cache to qemu.
The use case here is where non-local storage is used (e.g. rbd, ceph)
using the qemu drivers, together with a local cache as a file on
a much faster locally
On Mon, Apr 01, 2013 at 01:21:45PM +, Alex Bligh wrote:
> I'd like to experiment with adding persistent writeback cache to qemu.
> The use case here is where non-local storage is used (e.g. rbd, ceph)
> using the qemu drivers, together with a local cache as a file on
> a much faster locally mou
I'd like to experiment with adding persistent writeback cache to qemu.
The use case here is where non-local storage is used (e.g. rbd, ceph)
using the qemu drivers, together with a local cache as a file on
a much faster locally mounted device, for instance an SSD (possibly
replicated). This would
15 matches
Mail list logo
