[prev in list] [next in list] [prev in thread] [next in thread] 

List:       oprofile-commits
Subject:    [oprof-cvs] [SF SCMS]oprofile branch master updated. 492e520dd4763a6bb77ff9f8b91f0fd766ed9834
From:       "Maynard Johnson" <maynardj () users ! sourceforge ! net>
Date:       2014-02-07 23:20:48
Message-ID: E1WBujB-00035R-GB () sfs-ml-4 ! v29 ! ch3 ! sourceforge ! com
[Download RAW message or body]

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "oprofile".

The branch, master has been updated
       via  492e520dd4763a6bb77ff9f8b91f0fd766ed9834 (commit)
      from  31389d9cf7c0946479065e0baf0efd52cc4ba1f4 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 492e520dd4763a6bb77ff9f8b91f0fd766ed9834
Author: Maynard Johnson <maynardj@us.ibm.com>
Date:   Fri Feb 7 17:02:41 2014 -0600

    Enhance ocount to support millisecond time intervals
    
    The ocount tool currently has a --time-interval option that
    allows users to print a snapshot of event counts every n seconds,
    where 'n' is an integer value equal to or greater than 1.
    A user requested a change to allow time intervals of 100 ms.
    The user stated that he uses an event counting tool on a
    non-Linux operating system, and that tool had the option of
    collecting counts every 100 ms. Now, he wanted the same ability
    on Linux so he could do direct comparison of data. The
    original choice of one second granularity for the time interval
    option was arbitrary, so the request (based on a real world
    use case) seemed reasonable.
    
    This patch changes ocount's '--time-interval' option to accept
    values in units of milliseconds instead of seconds. At this
    time, the implementation supports only 100 ms granularity, so
    time intervals passed will be rounded to the nearest 100 ms.
    
    NOTE: Current users of ocount who make use of the '--time-interval'
    option will see a change in behavior. I don't believe this is
    a serious compatibility issue since the timestamp printed along
    with the event counts makes it very clear what the actual
    time interval is, and the user can check the ocount man page
    for clarification.
    
    Signed-off-by: Maynard Johnson <maynardj@us.ibm.com>

-----------------------------------------------------------------------

Summary of changes:
 doc/ocount.1.in        |   25 ++++++++---
 doc/oprofile.xml       |   24 ++++++++---
 pe_counting/ocount.cpp |  104 ++++++++++++++++++++++++++++++++++++++++++-----
 3 files changed, 128 insertions(+), 25 deletions(-)


hooks/post-receive
-- 
oprofile

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________
Oprofile-commits mailing list
Oprofile-commits@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oprofile-commits
[prev in list] [next in list] [prev in thread] [next in thread]