Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 Mar 2015 21:00:54 +0000 (UTC)
From:      "Kenneth D. Merry" <ken@FreeBSD.org>
To:        src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-10@freebsd.org
Subject:   svn commit: r279545 - stable/10/lib/libdevstat
Message-ID:  <201503022100.t22L0sv4094745@svn.freebsd.org>

next in thread | raw e-mail | index | archive | help
Author: ken
Date: Mon Mar  2 21:00:54 2015
New Revision: 279545
URL: https://svnweb.freebsd.org/changeset/base/279545

Log:
  MFC r279346:
  
    ------------------------------------------------------------------------
    r279346 | ken | 2015-02-26 19:44:12 -0700 (Thu, 26 Feb 2015) | 13 lines
  
    Remove an obsolete comment in devstat(3) about the accuracy of the
    milliseconds per transaction (DSM_MS_PER_TRANSACTION) calculation.
  
    The comment was accurate many years ago when the kernel didn't
    record I/O times on a per-I/O basis, but now that we do collect
    that information in most areas, it isn't correct.
  
    The milliseconds per transaction values are correct, assuming the
    I/O duration has been recorded.
  
    Sponsored by:	Spectra Logic
  
    ------------------------------------------------------------------------

Modified:
  stable/10/lib/libdevstat/devstat.c
Directory Properties:
  stable/10/   (props changed)

Modified: stable/10/lib/libdevstat/devstat.c
==============================================================================
--- stable/10/lib/libdevstat/devstat.c	Mon Mar  2 20:42:06 2015	(r279544)
+++ stable/10/lib/libdevstat/devstat.c	Mon Mar  2 21:00:54 2015	(r279545)
@@ -1480,22 +1480,9 @@ devstat_compute_statistics(struct devsta
 				*destld = 0.0;
 			break;
 		/*
-		 * This calculation is somewhat bogus.  It simply divides
-		 * the elapsed time by the total number of transactions
-		 * completed.  While that does give the caller a good
-		 * picture of the average rate of transaction completion,
-		 * it doesn't necessarily give the caller a good view of
-		 * how long transactions took to complete on average.
-		 * Those two numbers will be different for a device that
-		 * can handle more than one transaction at a time.  e.g.
-		 * SCSI disks doing tagged queueing.
-		 *
-		 * The only way to accurately determine the real average
-		 * time per transaction would be to compute and store the
-		 * time on a per-transaction basis.  That currently isn't
-		 * done in the kernel, and would only be desireable if it
-		 * could be implemented in a somewhat non-intrusive and high
-		 * performance way.
+		 * Some devstat callers update the duration and some don't.
+		 * So this will only be accurate if they provide the
+		 * duration. 
 		 */
 		case DSM_MS_PER_TRANSACTION:
 			if (totaltransfers > 0) {
@@ -1505,11 +1492,6 @@ devstat_compute_statistics(struct devsta
 			} else
 				*destld = 0.0;
 			break;
-		/*
-		 * As above, these next two really only give the average
-		 * rate of completion for read and write transactions, not
-		 * the average time the transaction took to complete.
-		 */
 		case DSM_MS_PER_TRANSACTION_READ:
 			if (totaltransfersread > 0) {
 				*destld = totaldurationread;



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201503022100.t22L0sv4094745>