Analysis of SPDK-originated patches to DPDK fork spdk-18.08
by Lance Hartmann ORACLE
I've put together a spreadsheet (attached) and a PDF as well for folks who'd rather not open Excel attachments.
The point of this exercise was to identify the SPDK-originated patches to the SPDK's fork of the DPDK (branch spdk-18.08), and then attempt to determine whether:
• they had been accepted in upstream DPDK 18.11
• they were cherry-pick'd forward to SPDK's fork of DPDK (branch spdk-18.11)
• they've appeared in upstream DPDK-stable as of tag v18.08.1-rc3
• they've appeared in upstream DPDK-stable as of tag v18.11.1-rc1
• they've appeared in upstream DPDK-stable as of tag v19.02-rc1
I had hoped that I might be able to build SPDK 18.10.1 against the forthcoming, pure upstream DPDK v18.08.1, but then after the email exchange with Jim who had forwarded email from Bruce Richardson and Ferruh Yigit, I was prompted to consider building against pure upstream DPDK v18.11 (or forthcoming pure upstream DPDK v18.11.1).
However, in any of those cases, it appears the following SPDK-originated patches to SPDK's fork of DPDK branch spdk-18.08 have not been promoted to any of the upstream DPDK branches/tags, but instead only carried as cherry-pick's to our fork of DPDK branch spdk-18.11 (or apparently nowhere further at all) so I'd like to understand the deeper ramifications of them so that I may decide whether to include them as rpm patches to a custom DPDK build. For some I'm fairly certain I can ignore as they're either crypto or BSD-related, but some of them I've marked as "unknown ???" because I don't know what I should do about them.
fork DPDK branch spdk-18.08 hash (description)
======================================
fbde197 (dpdk: temp hacks to enable SPDK crypto vbdev)
- Planning to ignore this as I will configure/build SPDK 18.10.1 without crypto enabled.
895f630 (Revert "contigmem: do not zero pages during each mmap")
- Planning to ignore as this is only related to BSD.
4275b1a (RHEL 6.4 support - use previous 'deprecated' attibute API)
- unknown ???
4c617c2 (memory: implement "single file segments" for legacy mem mode)
- unknown ???
632bbe7 (vfio: don't map single-segment hugepage memory in legacy mem mode)
- unknown ???
812c579 (Revert "crypto/aesni_mb: call buffer manager allocation")
- Planning to ignore this as I will configure/build SPDK 18.10.1 without crypto enabled.
73fadf0 (crypto: allow memzone to be created from secondary process)
- Planning to ignore this as I will configure/build SPDK 18.10.1 without crypto enabled.
96fae0e (pci_common_uio: store the pci dev address in secondary processes)
- Planning to ignore this as I will configure/build SPDK 18.10.1 without crypto enabled. Issue for QAT cards when using crypto drivers.
thanks,
--
Lance Hartmann
lance.hartmann(a)oracle.com
2 years
U.S. Summit - April 16th and 17th 2019
by Walker, Benjamin
We're excited to officially announce the third annual U.S. Summit!
We are very fortunate to have received a large number of abstracts for SPDK
talks, so the conference will be jam-packed with talks from all across the
storage industry. The topics will range from cutting edge new development to
experiences with deploying in production. A full agenda will be available
shortly.
This year the summit is expanding with three parallel tracks to cover a wide
range of topics. We are especially excited to have developers from the PMDK
community join us for several talks on persistent memory in one track, as well
as developers from Intel VTune Amplifier discussing performance monitoring and
optimization tools for both storage and persistent memory in another track.
April 16-17
Dolce Hayes Mansion
200 Edenvale Ave, San Jose, CA 95136
(408) 226-3200
Register Here: http://cvent.com/d/3bqgy8
The summit remains free to attend. If you plan to book a room at the hotel, we
do ask that you do it through the conference registration system.
2 years
ci.spdk.io downtime
by Zawadzki, Tomasz
Hello everyone,
We're experiencing issues with ci.spdk.io domain.
Detailed Jenkins CI logs and build artifacts will not be available at this time.
Access to SDPK webpage on that domain remains unaffected.
Verified score from Jenkins CI on submitted patches remains unaffected.
We'll send out an information when everything is back to normal.
Thank you,
Tomek
2 years
spdk_dma_malloc deprecation notice
by Stojaczyk, Dariusz
Next week I'd like to deprecate spdk_dma_*malloc() and replace its existing usages with spdk_*malloc() which has slightly different signature.
If you have any pending patches that still use spdk_dma_*malloc(), please consider switching to spdk_*malloc().
Thanks,
D.
2 years
How to use QEMU and the FTL library?
by Derrick
Hello,
I was trying to play around the the FTL code in the latest SPDK release.In the documentation (SPDK: Flash Translation Layer) it states that the easiest way is to create an emulated OpenChannel drive using the SPDK's QEMU fork on branch spdk-3.0.0. I checked out the repo, but I don't see any changes related to adding support for OpenChannel. Furthermore, the flags provided in the example don't exist in the source, and attempting to pass them generate an error when starting QEMU. Is there something additional I must to do get OepnChannel SSD support into the QEMU branch?
Thanks,David
|
|
| |
SPDK: Flash Translation Layer
|
|
|
2 years
