December 2021 - SPDK - Ml01.01.Org

December 28th bug scrub meeting cancelled

by Zawadzki, Tomasz

Hello everyone, There are several usual attendees out tomorrow, so the SPDK bug scrub meeting is cancelled. See you in the new year on the next Euro-Friendly Community Meeting - January 4th, 2022. Thanks, Tomek

2 weeks

2
1
0 / 0

CANCELLED: Asia-Friendly Community Meeting Thursday, December 30, 2021, 12:00 PM GMT+8

by Liu, Changpeng

Hello everyone, The next Asia-Friendly Community Meeting Thursday, December 30, 2021, 12:00 PM GM will be cancelled.

4 weeks, 1 day

1
0
0 / 0

Query regarding nvme_tcp_read_data() API.

by Senthil Kumar Veluswamy

Hi, In the SPDKv20.07, I’ve query on the below code. In this nvme_tcp_read_data(), if spdk_sock_recv() return “0” i.e. ret = 0, then it treats that condition as FATAL and the caller of nvme_tcp_read_data() i.e. nvmf_tcp_sock_process(), disconnects the connection. So, would like to know why this condition is treated as FATAL condition and disconnect is issued [as readv() can return ZERO bytes]? static int nvme_tcp_read_data(struct spdk_sock *sock, int bytes, void *buf) { int ret; ret = spdk_sock_recv(sock, buf, bytes); if (ret > 0) { return ret; } if (ret < 0) { if (errno == EAGAIN || errno == EWOULDBLOCK) { return 0; } /* For connect reset issue, do not output error log */ if (errno != ECONNRESET) { SPDK_ERRLOG("spdk_sock_recv() failed, errno %d: %s\n", errno, spdk_strerror(errno)); } } /* connection closed */ return NVME_TCP_CONNECTION_FATAL; } Thanks, Senthil Kumar V.

1 month, 1 week

3
4
0 / 0

Operations on ZNS

by yashy.zb＠gmail.com

Hi. I have some questions about the ZNS APIs. 1. Do I need to call `spdk_nvme_zns_open_zone` before `spdk_nvme_zns_zone_append` when I intend to write data? What about reading? 2. Do I have full control on calling `spdk_nvme_zns_reset_zone`? Thanks

1 month, 1 week

1
0
0 / 0

New SPDK core maintainer - Konrad Sztyber

by Harris, James R

The SPDK project has a team of core maintainers who are responsible for providing technical oversight for the SPDK project, including final review and merging of patches into the SPDK code base. As the SPDK project continues to grow, the core maintainer team also needs to grow by adding contributors who are already demonstrating technical skill and leadership within the project. So we are pleased to announce that we are adding Konrad Sztyber to the core maintainer team! Konrad has been a key contributor to SPDK with a special focus on the NVMe driver, tracing infrastructure, Intel VMD driver and FTL. Konrad is also a key reviewer across a variety of SPDK libraries and components. Konrad is from Intel and is based in Gdansk, Poland. Thanks, Jim Harris (representing the core maintainer team) Please visit Core Maintainers<http://www.spdk.io/development/#core> for further details on the core maintainer team and their responsibilities.

1 month, 2 weeks

1
0
0 / 0

--no-huge on IOMMU/VFIO platform

by niketkandya＠google.com

From my reading of the code and docs this is what I understand: 1. Huge pages are needed by SPDK/DPDK so that user pages are always present and pinned. 2. In systems with IOMMU and VFIO support, there should be no need for huge pages. spdk_mem_register on an externally allocated buffer should do the same pinning. 3. This is also what happens to DPDK's internal heaps in the memory callbacks (memory_iter_cb). When I tried to use --no-huge with SPDK it failed with error in alignment/size restrictions for DPDK's internal heap. I was able to hack DPDK code to return 2MB aligned addresses for its internal heap and this worked. So, to confirm my understanding here: for SPDK to work without hugepages, just a guarantee that (2MB)aligned addresses are returned by DPDK's internal heap should be enough?

1 month, 3 weeks

2
1
0 / 0

2022

2021

2020

2019

2018

2017

2016

SPDK December 2021