[PATCH] Min/Max in numademo output is confusing

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

Original Min/Max in numademo output is confusing. The 'Min' meant the
minimum time the operation have been occupied, while the printed numbers 
are bandwidth data, which has reversed meaning in terms of quantity.

Reverting Min/Max in the print message is better.

Signed-off-by: Kent Liu <kent.liu@xxxxxxxxxxxxxxx>
---
 numademo.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/numademo.c b/numademo.c
index 9c3ef70..df937d5 100755
--- a/numademo.c
+++ b/numademo.c
@@ -249,7 +249,7 @@ void memtest(char *name, unsigned char *mem)
 	sprintf(title, "%s%s%s", name, delim, testname[thistest]); 
 #define H(t) (((double)msize) / ((double)t))
 #define D3 delim,delim,delim
-	sprintf(result, "Avg%s%.2f%sMB/s%sMin%s%.2f%sMB/s%sMax%s%.2f%sMB/s",
+	sprintf(result, "Avg%s%.2f%sMB/s%sMax%s%.2f%sMB/s%sMin%s%.2f%sMB/s",
 		delim,
 		H(sum/LOOPS), 
 		D3,
--
To unsubscribe from this list: send the line "unsubscribe linux-numa" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]     [Devices]

  Powered by Linux