Peter Tribble wrote:
>On 10/9/07, Cathy Zhou <[EMAIL PROTECTED]> wrote:
>
>>>Today if I'm given a network interface name of "bge0", the most
>>>correct way to ask kstat about it is to use a call like this:
>>>
>>>kstat_lookup(kc, "bge", 0, "bge0")
>>>
>>>
>>Note that this would still work (if vanity naming is not used), as we kept
>>the "legacy" kstats.
>>
>>The things won't work is that if you renamed bge0 to net0, and tries to
>>lookup its kstat using kstat_lookup(kc, "net", 0, "net0").
>>
>
>[Sorry, catching up.]
>
>So, if a user renames bge0 to net0, what kstats exist?
>
>Does bge:0:bge0 exist? Does bge:0:net0 exist?
>
>If the kstat names change, does the accumulated data transfer to
>the new kstat? How can I tell that a kstat has changed name?
>
I changed the name of bge0 to bugbear0, and this is what
can be seen:
$ kstat -n bge0
module: bge instance: 0
name: bge0 class: net
brdcstrcv 13701
brdcstxmt 72
collisions 0
crtime 55.229061029
ierrors 0
ifspeed 100000000
ipackets 15513
ipackets64 15513
link_duplex 2
link_state 1
multircv 132
multixmt 2
norcvbuf 0
noxmtbuf 0
obytes 207417
obytes64 207417
oerrors 0
opackets 1703
opackets64 1703
rbytes 1856504
rbytes64 1856504
snaptime 13660.164025055
unknowns 7
$ kstat -n bugbear0
module: link instance: 0
name: bugbear0 class: net
brdcstrcv 13704
brdcstxmt 72
collisions 0
crtime 55.229137696
ierrors 0
ifspeed 100000000
ipackets 15552
ipackets64 15552
link_duplex 2
link_state 1
multircv 132
multixmt 2
norcvbuf 0
noxmtbuf 0
obytes 212029
obytes64 212029
oerrors 0
opackets 1737
opackets64 1737
rbytes 1859546
rbytes64 1859546
snaptime 13666.167247049
unknowns 7
Darren
_______________________________________________
networking-discuss mailing list
[email protected]
