Storage Performance Development Kit (SPDK)
 help / color / mirror / Atom feed
* [SPDK] QEMU OCSSD fork
@ 2019-02-25 12:07 Klaus Birkelund
  0 siblings, 0 replies; 3+ messages in thread
From: Klaus Birkelund @ 2019-02-25 12:07 UTC (permalink / raw)
  To: spdk

[-- Attachment #1: Type: text/plain, Size: 659 bytes --]

Hi,

The FTL document[1] mentions an SPDK QEMU fork[2] with OCSSD patches.
There does not seem to be any patches in that repo though.

I'm a contributor on the qemu-nvme[2] project which also provides an
emulated OCSSD device (only 2.0). We have recently added a lot of
features (SGLs, predefined data, support for DULBE, error injection). If
the SPDK team has a similar but unpublished fork would you consider
releasing it? I would be happy to see if it made sense to try and
consolidate our work on the forks.


  [1]: https://github.com/spdk/spdk/blob/master/doc/ftl.md
  [2]: https://github.com/OpenChannelSSD/qemu-nvme


Cheers,
Klaus

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [SPDK] QEMU OCSSD fork
@ 2019-02-25 12:28 Zawadzki, Tomasz
  0 siblings, 0 replies; 3+ messages in thread
From: Zawadzki, Tomasz @ 2019-02-25 12:28 UTC (permalink / raw)
  To: spdk

[-- Attachment #1: Type: text/plain, Size: 1497 bytes --]

Hi Klaus,

You are correct that our documentation specifies there are patches for QEMU in our QEMU fork. They are in process of being reviewed, which for SPDK is done on GerritHub [1].

My understanding is that the patches are based on the same implementation in qemu-nvme [2]. They have been rebased on QEMU 3.0.0 with some minor changes.

[1]: https://review.gerrithub.io/#/q/status:open+project:spdk/qemu+branch:spdk-3.0.0
[2]: https://github.com/OpenChannelSSD/qemu-nvme

Thanks,
Tomek

-----Original Message-----
From: SPDK [mailto:spdk-bounces(a)lists.01.org] On Behalf Of Klaus Birkelund
Sent: Monday, February 25, 2019 1:08 PM
To: spdk(a)lists.01.org
Subject: [SPDK] QEMU OCSSD fork

Hi,

The FTL document[1] mentions an SPDK QEMU fork[2] with OCSSD patches.
There does not seem to be any patches in that repo though.

I'm a contributor on the qemu-nvme[2] project which also provides an emulated OCSSD device (only 2.0). We have recently added a lot of features (SGLs, predefined data, support for DULBE, error injection). If the SPDK team has a similar but unpublished fork would you consider releasing it? I would be happy to see if it made sense to try and consolidate our work on the forks.


  [1]: https://github.com/spdk/spdk/blob/master/doc/ftl.md
  [2]: https://github.com/OpenChannelSSD/qemu-nvme


Cheers,
Klaus
_______________________________________________
SPDK mailing list
SPDK(a)lists.01.org
https://lists.01.org/mailman/listinfo/spdk

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [SPDK] QEMU OCSSD fork
@ 2019-02-25 12:44 Klaus Birkelund
  0 siblings, 0 replies; 3+ messages in thread
From: Klaus Birkelund @ 2019-02-25 12:44 UTC (permalink / raw)
  To: spdk

[-- Attachment #1: Type: text/plain, Size: 658 bytes --]

On Mon, Feb 25, 2019 at 12:28:47PM +0000, Zawadzki, Tomasz wrote:
> Hi Klaus,
> 
> You are correct that our documentation specifies there are patches for QEMU in our QEMU fork. They are in process of being reviewed, which for SPDK is done on GerritHub [1].
> 
> My understanding is that the patches are based on the same implementation in qemu-nvme [2]. They have been rebased on QEMU 3.0.0 with some minor changes.
> 
> [1]: https://review.gerrithub.io/#/q/status:open+project:spdk/qemu+branch:spdk-3.0.0
> [2]: https://github.com/OpenChannelSSD/qemu-nvme
> 
> Thanks,
> Tomek
> 

Hi Tomek,

Thanks! That makes sense.


Cheers,
Klaus


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2019-02-25 12:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-02-25 12:44 [SPDK] QEMU OCSSD fork Klaus Birkelund
  -- strict thread matches above, loose matches on Subject: below --
2019-02-25 12:28 Zawadzki, Tomasz
2019-02-25 12:07 Klaus Birkelund

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox