From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============1139964172765194669==" MIME-Version: 1.0 From: Walker, Benjamin Subject: Re: [SPDK] 3dxpoint & spdk? Date: Thu, 11 Feb 2016 22:37:16 +0000 Message-ID: <1455230236.61425.219.camel@intel.com> In-Reply-To: CAHxARCHevSp4hQDT3Jp2TWoSM=eBfvR-CEhVLHkvSoRY+2G3Dg@mail.gmail.com List-ID: To: spdk@lists.01.org --===============1139964172765194669== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hi Michael, If a 3D XPoint based NVMe drive was released, using SPDK's NVMe driver woul= d be an excellent choice for getting the best possible performance inside o= f a dedicated storage application. The SPDK NVMe driver should work with an= y device that is compliant with the NVMe specification. This includes any p= otential upcoming 3D XPoint based devices, but also current NAND-based devi= ces and possibly even the emulated NVMe device available through QEMU. We c= urrently test the SPDK NVMe driver against Intel P3700 series SSDs, so I ca= nnot make any guarantees that the driver works in other environments. If yo= u try and find any problems, please do send us patches! Thanks, Ben On Thu, 2016-02-11 at 14:20 -0800, Michael Xu wrote: hi everyone, i am curious as to whether spdk would be the right library to be using to a= ccess 3dxpoint, once 3d xpoint comes out and becomes publicly available... = given both spdk and 3dxpoint come from intel, and spdk is all about getting= as much performance as possible from nvme storage devices. should i be lo= oking at using the nvme specific driver? also, is there any ability to fake the presence of devices? I frequently ru= n in virtualized environments, and it would be great to be able to interact= and use the API without requiring a physical NVME device connected. regards, michael -- Michael Xu michael(a)michaelxu.co _______________________________________________ SPDK mailing list SPDK(a)lists.01.org https://lists.01.org/mailman/listinfo/spdk --===============1139964172765194669==--