From: Yaowei Bai <baiyaowei@cmss.chinamobile.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: fam@euphon.net, kwolf@redhat.com, qemu-block@nongnu.org,
qemu-devel@nongnu.org, mreitz@redhat.com,
yangjun@cmss.chinamobile.com, baiyaowei@cmss.chinamobile.com,
dillaman@redhat.com
Subject: Re: COMPARE_AND_WRITE support for rbd driver
Date: Fri, 20 Sep 2019 23:26:28 +0800 [thread overview]
Message-ID: <20190920152627.GA10350@byw> (raw)
In-Reply-To: <8a304065-b9ec-8245-09ae-e38724f46645@redhat.com>
On Fri, Sep 20, 2019 at 01:22:02PM +0200, Paolo Bonzini wrote:
> On 19/09/19 07:36, Yaowei Bai wrote:
> >
> > Hey guys,
> >
> > I noticed that COMPARE_AND_WRITE had been supported by CEPH/librbd since
> > v12.1.1. And in my company, we use this COMPARE_AND_WRITE support in
> > CEPH with the ISCSI protocol. More precisely, we use tgt and CEPH with this
> > COMPARE_AND_WRITE support as the SCSI target and export it to the remote
> > hosts. And then VMs on remote hosts can use these SCSI targets through ISCSI
> > initiator support in QEMU directly or as local SCSI disks. But unfortunately,
> > there're some issues with this tgt case. So i think maybe we could also add this
> > COMPARE_AND_WRITE support into the rbd driver in QEMU so we can leave the
> > ISCSI/tgt alone and use this COMPARE_AND_WRITE support with the
> > scsi-disk <--> virtio-scsi <--> rbd driver path. This can also apply to
> > the WRITESAME support in CEPH/librbd.
> >
> > So is it suitable for doing this?
>
> Yes, it would be suitable. In a nutshell you would have to add support
> for COMPARE_AND_WRITE to block/io.c (calling into a new BlockDriver
> function pointer), block/rbd.c and hw/scsi/scsi-disk.c.
OK, i'll try to implement this and send it out for review. Thanks Paolo.
>
> Paolo
prev parent reply other threads:[~2019-09-20 15:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 5:36 [Qemu-devel] COMPARE_AND_WRITE support for rbd driver Yaowei Bai
2019-09-20 11:22 ` Paolo Bonzini
2019-09-20 15:26 ` Yaowei Bai [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=20190920152627.GA10350@byw \
--to=baiyaowei@cmss.chinamobile.com \
--cc=dillaman@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=yangjun@cmss.chinamobile.com \
/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.