pcp
[Top] [All Lists]

Re: Performance Co-Pilot patch for Compaq's Tru64

To: Mark Goodwin <markgw@xxxxxxx>
Subject: Re: Performance Co-Pilot patch for Compaq's Tru64
From: Phillip Ezolt <ezolt@xxxxxxxxxxxxxxxx>
Date: Wed, 29 Aug 2001 13:29:15 -0400 (EDT)
Cc: <pcp@xxxxxxxxxxx>
In-reply-to: <Pine.LNX.4.21.0108290734350.7594-100000@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-pcp@xxxxxxxxxxx
Mark,

> please use 75 (74 is used by lmsensors).
>

Ok.  I'll change my code here.

One question for you, I am trying to implement the osf code as close
as possible to the Linux code.

I'm trying to keep as many metrics as possible the same.

What should I do with NEW metrics?  Is it ok to add them, or is there some
reason not to?

For example, in the network driver, Tru64 can provide the following information
for Multi-casts:

0 Multicast Packets Recvd              0 Multicast Bytes Received
0 Multicast Packets Sent               0 Multicast Bytes Sent

However, network.interface.out

network.interface.out {
    bytes               60:3:8
    packets             60:3:9
    errors              60:3:10
    drops               60:3:11
    fifo                60:3:12
    carrier             60:3:14
    compressed          60:3:15
}

doesn't say ANYTHING about:

network.interface.out.mcast.packets
network.interface.out.mcast.bytes

Should I just add it, or is there some standard that we should agree on?

--Phil

Compaq:   High Performance Server Systems Quality & Performance Engineering
---------------- Alpha, The Fastest Processor on Earth --------------------
Phillip.Ezolt@xxxxxxxxxx                         Performance Tools/Analysis
------------------- See the results at www.spec.org -----------------------



<Prev in Thread] Current Thread [Next in Thread>