From: Wei Liu <wei.liu2@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@citrix.com>
Subject: Re: [PATCH RESEND] tools/libxl: add support for emulated NVMe drives
Date: Thu, 19 Jan 2017 11:18:42 +0000 [thread overview]
Message-ID: <20170119111842.GI5089@citrix.com> (raw)
In-Reply-To: <e5d57a8daaeb4f4ba4d790e4a6207b65@AMSPEX02CL03.citrite.net>
On Thu, Jan 19, 2017 at 08:58:12AM +0000, Paul Durrant wrote:
> > -----Original Message-----
> [snip]
> > > > For safety I guess I could explore the possibility of having libxl not
> > > > create a PV backend for this vdev type.
> > >
> > > ... this is the best option for now.
> > >
> >
> > And I realise if we are not going to have code in libxl for nvme pv
> > disk, we can just use device_model_args to add the emulated device,
> > which means this patch is not needed anymore.
> >
>
> device_model_args is not exactly a user-friendly way to use emulated nvme disks, which was the main motivation for this patch.
>
> > Can you clarify the use case you anticipated for emulated NVMe disks?
> >
>
> My personal use is going to be to test performance, and maybe try to improve. The advantage with NVMe over PV is that the perf. is already not bad, and there's no need to install PV storage drivers since recent versions of Windows (and other OS) already have NVME drivers. The main problem with them is that seabios cannot (yet) boot from NVMe. I'm hoping OVMF might, but I need to experiment further.
> Given the push-back I guess I'll live with the device_model_args hassle for the moment and re-send once I've got an unplug patch into QEMU.
>
Thanks for clarification. It's best to resubmit until QEMU patch is
ready.
Wei.
> Paul
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-01-19 11:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 14:00 [PATCH RESEND] tools/libxl: add support for emulated NVMe drives Paul Durrant
2017-01-18 10:28 ` Wei Liu
2017-01-18 10:51 ` Paul Durrant
2017-01-18 12:02 ` Wei Liu
2017-01-18 12:15 ` Paul Durrant
2017-01-18 12:20 ` Wei Liu
2017-01-18 15:07 ` Wei Liu
2017-01-19 8:58 ` Paul Durrant
2017-01-19 11:18 ` Wei Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-22 13:09 Paul Durrant
2017-03-22 14:16 ` Ian Jackson
2017-03-22 14:22 ` Paul Durrant
2017-03-22 15:01 ` Ian Jackson
2017-03-22 15:21 ` Paul Durrant
2017-03-22 16:03 ` Ian Jackson
2017-03-22 16:31 ` Paul Durrant
2017-03-22 16:45 ` Paul Durrant
2017-03-22 17:02 ` Ian Jackson
2017-03-22 17:16 ` Paul Durrant
2017-03-22 17:31 ` Ian Jackson
2017-03-22 17:41 ` Paul Durrant
2017-03-22 17:48 ` Ian Jackson
2017-03-23 8:55 ` Paul Durrant
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=20170119111842.GI5089@citrix.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).