Call for testers with NVMe

Hello Abdelkader,

Yes, it was my fault. The script I wrote for the test did increase -t
parameter instead of -n. I'm really sorry for providing misleading test
results. Will be more attentive next time. :$

Here below are new test results ran on 16.0-patched kernel. No problems
so far.

# uname -a
FreeBSD 16.0-CURRENT FreeBSD 16.0-CURRENT #1
drop_s3x_quirk_test-b90ba7e5f8f8: Sat Sep 19 21:26:27 +05 2026
rz@megamini:/home/rz/FreeBSD-src/src-current/obj/amd64.amd64/sys/GENERIC
amd64

# nvmecontrol devlist
nvme0: SAMSUNG MZALQ256HBJD-00BL2
nvme0ns1 (244198MB)

# nvmecontrol perftest -t 30 -n 16 -s 131072 -o read nvme0ns1
Threads: 16 Size: 131072 READ Time: 30 IO/s: 5941 MB/s: 742
# nvmecontrol perftest -t 30 -n 32 -s 131072 -o read nvme0ns1
Threads: 32 Size: 131072 READ Time: 30 IO/s: 11959 MB/s: 1494
# nvmecontrol perftest -t 30 -n 64 -s 131072 -o read nvme0ns1
Threads: 64 Size: 131072 READ Time: 30 IO/s: 13782 MB/s: 1722

---
Regards,
Ruslan 

>