Apologies for the formatting, but I have nodes on a 100Mb link and am
trying to understand the actual reading here. If it's in Kbits, then it
could make sense, but in KBytes, I don't see how 100Mb can do more than 12
MB/s.
#<----------Disks-----------> <----------Network---------->
#KBRead Reads KBWrit Writes KBIn PktIn KBOut PktOut
0 0 11448 90 21821 14098 575 6850
This is on a FC17 system with the latest kernel update as of yesterday.
$ rpm -q collectl
collectl-3.6.3-2.noarch
uname -r
3.6.1-1.fc17.x86_64
$ ethtool p1p1
Settings for p1p1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000033 (51)
drv probe ifdown ifup
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Collectl-interest mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/collectl-interest
