[Bug 240798] nvmecontrol perftest is broken

2019-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240798 Kubilay Kocak changed: What|Removed |Added Status|New |In Progress Assignee|b..

[Bug 240798] nvmecontrol perftest is broken

2019-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240798 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: imp Date: Wed Sep 25 00:24:57 UTC 2019 New revision: 352665 URL: https://svnweb.freebsd.org/changeset/base/352665 Log: After my comnd changes, the numb

[Bug 240798] nvmecontrol perftest is broken

2019-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240798 --- Comment #2 from Stefan Rink --- (In reply to olevole from comment #1) On FreeBSD 12 with the patched nvmecontrol from current I get; root@SuperBSD:/tmp/sbin # ./nvmecontrol perftest -n 12 -o read -s 16384 -t 30 nvme0ns1 Threads: 12 Siz

[Bug 240798] nvmecontrol perftest is broken

2019-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240798 --- Comment #1 from olev...@olevole.ru --- This patch should only fix the optional arguments, right? With/without patch I still get null values for nvme perftest on FreeBSD current: % uname -a FreeBSD test.my.domain 13.0-CURRENT FreeBSD 13

[Bug 240798] nvmecontrol perftest is broken

2019-09-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240798 Bug ID: 240798 Summary: nvmecontrol perftest is broken Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Som