At 09:42 PM 2/27/00 -0500, jamal wrote:
>So maybe BSD knows how to do this; not sure how vmstat -i works: i.e how
>accurate it is, what kind of measurement windows it is.
>Theres no way /proc/interrupts could tell you the rate.
#!/bin/sh
T3DEVICE=eth0
>interrupt.log
for h in 0 1 2 3 4 5 6 7 8 9 ; do
for r in 0 1 2 3 4 5 6 7 8 9 ; do
for t in 0 1 2 3 4 5 6 7 8 9 ; do
echo $h$r.$t = `cat /proc/interrupts | grep $T3DEVICE` >>interupt.log
sleep 360
done;
done;
done;
With a little EXCEL magic I can give you a histogram over the 100 hours
showing rate deviations over the test.
But I can do a little better, and get some additional information by using
"proc/net/dev" to capture the RX and TX packet rate (which is what we were
trying to measure, wasn't it?) and also see the error counters.
The interrupt rate might not be the best measure, because you could get
multiple interrupts per packet if the packet was large enough. I could
also see where you would get an interrupt when the transmit buffer was
exhausted and you had nothing more to transmit.
As a driver writer, I love to find ways to make every interrupt count, so I
would try to do multiple operations...which means that the interrupt count
could then underreport the packet transfer capability.
Now go ahead and tell me that your statement was a troll... :)
Satch
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
