I simply tested the BlobFS Asynchronous API by using SPDK events framework to execute multi tasks, each task writes one file.
But it doesn't work, the spdk_file_write_async() reported an error when resizing the file size.
The call stack looks like this:
spdk_file_write_async() -> __readwrite() -> spdk_file_truncate_async() -> spdk_blob_resize()
The resize operation must be done in the metadata thread which invoked the spdk_fs_load(), so only the task dispatched to the metadata CPU core works.
That's to say only one thread can be used to write files. It's hard to use, and performance issues may arise.
Does anyone knows further more about this?
thanks very much
SPDK Jenkins CI will be unavailable for a few hours on 2nd February.
Scheduled CI maintenance, updates, etc.
Downtime is scheduled at 2nd February 2022, 9:00AM GMT. It should not take more than a few hours, we plan to be back online by 1:00PM GMT.
How does that affect me?
Patches submitted to review.spdk.io will not be tested during downtime.
Sorry for the delay. It just got my attention while I try to debug a PDU error issue.
Senthil Kumar V.
On 17/01/22, 1:40 PM, "Zawadzki, Tomasz" <tomasz.zawadzki(a)intel.com> wrote:
CAUTION: This email originated from outside of Western Digital. Do not click on links or open attachments unless you recognize the sender and know that the content is safe.
Hi Senthil Kumar,
That patch was later reverted, see https://review.spdk.io/gerrit/c/spdk/spdk/+/5951 and corresponding GitHub Issue https://github.com/spdk/spdk/issues/1746.
Is there a reason why this particular patch got your attention ?
> -----Original Message-----
> From: Senthil Kumar Veluswamy <Senthil.Kumar.Veluswamy(a)wdc.com>
> Sent: Sunday, January 16, 2022 2:40 PM
> To: Storage Performance Development Kit <spdk(a)lists.01.org>
> Subject: [SPDK] Clarification regarding a TCP patch.
> I could see that the below patch removes await_req list and it got merged
> in Nov’2020.
> But I could still see the code in latest SPDK GIT repo. So would like to know
> the status of the same?
> Is this still required?
> Senthil Kumar V.
> SPDK mailing list -- spdk(a)lists.01.org
> To unsubscribe send an email to spdk-leave(a)lists.01.org
SPDK mailing list -- spdk(a)lists.01.org
To unsubscribe send an email to spdk-leave(a)lists.01.org
On behalf of the SPDK community I'm pleased to announce the release of SPDK 22.01 LTS!
The SPDK 22.01 release is a long term support release that will be supported for 1 year.
This release contains the following new features:
- NVMe bdev multipath: Added support for NVMe-oF multipath to bdev nvme.
- NVMe-oF TCP zero-copy: Added zero-copy support to NVMe-oF TCP transport.
- NVMe-oF discovery service: Added discovery service to bdev nvme. Allowing to connect to current and future subsystems added to discovery controller.
- IDXD transparent batching: Introduced performance optimizations, including transparently grouping independent operations into IDXD batch operations.
- vfio-user live migration: Added experimental support for virtual machine live migration to vfio-user NVMe-oF transport.
- iSCSI bdev resize: Added automatic block device resize detection to iSCSI bdev module.
- NVMe sparse namespaces: Improved handling of subsystems with sparsely populated active namespaces.
The full changelog for this release is available at:
This release contains 534 commits from 49 authors with over 25k lines of code changed.
We'd especially like to recognize all of our first time contributors:
Thanks to everyone for your contributions, participation, and effort!
The SPDK project has historically done quarterly releases, with an LTS release every January. To reduce the overhead burden of the release process, the SPDK project is planning to move to a 3x per year release cadence (every 4 months), starting with the next release – 22.05 in May 2022. SPDK would continue with an annual LTS release every January.
Note that this would also align SPDK with the newly adopted 3x per year DPDK release cadence. SPDK and DPDK releases will now alternate every two months (SPDK in January, DPDK in March, SPDK in May, etc.)
If you have any questions or concerns about the new release cadence, please let the core maintainers know, either here on the mailing list, or in one of the SPDK Slack channels.
Jim Harris (on behalf of the SPDK core maintainers)
Hi everyone! Just a short notice that SPDK Community CI will be offline for upcoming weekend.
Construction works in the building.
For how long?
SPDK CI will be powered down on Friday January 21st, 2:00PM GMT and will be back online on Monday January 24th, 8:00AM GMT.
How does that affect me?
SPDK CI will not pick up and test any patches send to review.spdk.io during downtime.
I could see that the below patch removes await_req list and it got merged in Nov’2020.
But I could still see the code in latest SPDK GIT repo. So would like to know the status of the same?
Is this still required?
Senthil Kumar V.