From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Yaowei Bai <baiyaowei@cmss.chinamobile.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Amar Tumballi <atumball@redhat.com>,
Mike Christie <mchristi@redhat.com>,
Prasanna Kalever <pkalever@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, Xiubo Li <xiubli@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH] tcmu: Introduce qemu-tcmu utility
Date: Thu, 7 Mar 2019 11:34:55 +0100 [thread overview]
Message-ID: <20190307103455.GA5786@linux.fritz.box> (raw)
In-Reply-To: <20190307102206.GC2843@stefanha-x1.localdomain>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
Am 07.03.2019 um 11:22 hat Stefan Hajnoczi geschrieben:
> On Wed, Mar 06, 2019 at 10:56:33PM +0100, Kevin Wolf wrote:
> > Am 21.12.2018 um 11:16 hat Yaowei Bai geschrieben:
> > * The first priority should be adding an in-process iscsi target that
> > can be managed with QMP, similar to the built-in NBD server.
>
> Using the in-kernel SCSI target with TCMU, or do you mean implementing
> the iSCSI network protocol inside QEMU?
Using TCMU in this case, of course. This point was about external tool
vs. exporting from a running QEMU instance, not about how to implement
the actual functionality.
Building an external command line tool around QMP functionality is easy,
but the reverse way isn't necessarily. This is why I think QMP-based
should come first.
Kevin
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2019-03-07 10:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 10:16 [Qemu-devel] [PATCH] tcmu: Introduce qemu-tcmu utility Yaowei Bai
2018-12-26 7:59 ` no-reply
2018-12-26 8:19 ` no-reply
2019-01-02 1:53 ` Yaowei Bai
2019-03-06 21:56 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2019-03-07 8:20 ` Yaowei Bai
2019-03-07 8:44 ` Yaowei Bai
2019-03-07 11:25 ` Kevin Wolf
2019-03-08 7:22 ` Yaowei Bai
2019-03-08 10:08 ` Kevin Wolf
2019-03-09 1:46 ` Yaowei Bai
2019-03-11 11:06 ` Kevin Wolf
2019-03-12 2:18 ` Fam Zheng
2019-03-07 10:22 ` Stefan Hajnoczi
2019-03-07 10:34 ` Kevin Wolf [this message]
2019-03-11 9:55 ` Stefan Hajnoczi
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=20190307103455.GA5786@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=atumball@redhat.com \
--cc=baiyaowei@cmss.chinamobile.com \
--cc=mchristi@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pkalever@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=xiubli@redhat.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.