History log of /freebsd/sbin/nvmecontrol/telemetry.c (Results 1 – 2 of 2)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# 3d966ae7 11-May-2024 Warner Losh <imp@FreeBSD.org>

nvmecontrol: Appease a meaningless signed error warning thing

Consistently use the weird ssize_t type for things I know are unsigned,
but which none-the-less need to be compared to signed things to

nvmecontrol: Appease a meaningless signed error warning thing

Consistently use the weird ssize_t type for things I know are unsigned,
but which none-the-less need to be compared to signed things to prevent
a bogus warning. Sigh, these aren't bugs, can't possibly be bugs and
a waste of time to fix.

Sponsored by: Netflix

show more ...


Revision tags: vendor/unbound/1.20.0, vendor/one-true-awk/a3b68e649d2d, vendor/llvm-project/llvmorg-18.1.5-0-g617a15a9eac9, vendor/libfido2/1.14.0, vendor/NetBSD/bmake/20240430, vendor/libcbor/0.11.0, vendor/llvm-project/llvmorg-18.1.4-0-ge6c3289804a6, vendor/device-tree/6.8, vendor/device-tree/6.7
# c1fccf0f 08-Apr-2024 Warner Losh <imp@FreeBSD.org>

nvmecontrol: Implement telemetry-log command.

This produces the same data as the Linux nvme-cli 'nvme telemetry-log'
command. It extracts the telemetry log from drive. This is a variable
length log,

nvmecontrol: Implement telemetry-log command.

This produces the same data as the Linux nvme-cli 'nvme telemetry-log'
command. It extracts the telemetry log from drive. This is a variable
length log, so we read the first page and find out how much of the log
to grab. There's 3 levels of details available, and we grab the level of
detail specified on the command line.

Sponsored by: Netflix

show more ...