The merge window for SPDK 22.09 release will close by September 23rd.
Please ensure all patches you believe should be included in the release are merged to 'master' branch by this date.
You can do it by adding a hashtag '22.09' in Gerrit on those patches.
The current set of patches that are tagged and need to be reviewed can be seen here:
On September 23rd new branch 'v22.09.x' will be created, and a patch on it will be tagged as release candidate.
Then, by September 30th, a formal release will take place tagging the last patch on the branch as SPDK 22.09.
Between release candidate and formal release, only critical fixes shall be backported to the 'v22.09.x' branch.
Development can continue without disruptions on 'master' branch.
During my daily use I found the tracing system of SPDK and spdk_trace_record
very low overhead. So I’m planning to port to other applications where it
might generate several 100K events per second. I think such a speed should
be normal for SPDK applications. Have you ever measured how many events per
second is spdk_trace able to handle?
I submitted the following two patches to the community last month,
This patch, I got Code-review -1 vote from maintainer this week, but I think my modification is reasonable, and I also responded in the comments of gerrit, I hope to receive some feedback.
This patch, I got one Code-Review +2 vote this week, so I hope to get more reviews to be merged as soon as possible. After all, this modification code is not much, and it has been submitted for about one month.