Tom Chen wrote: > Hmm, I did some extensive tests then made a core dump, no leak? > > -bash-3.00# mdb -k 32 > Loading modules: [ unix genunix specfs dtrace ufs sd mpt px ldc ip hook > neti sctp arp usba fcp fctl qlc nca lofs zfs nfs cpc random crypto ptm > sppp ] >> ::findleaks -dv > findleaks: maximum buffers => 783106 > findleaks: actual buffers => 722155 > findleaks: > findleaks: potential pointers => 77430152 > findleaks: dismissals => 68481241 (88.4%) > findleaks: misses => 500836 ( 0.6%) > findleaks: dups => 7725920 ( 9.9%) > findleaks: follows => 722155 ( 0.9%) > findleaks: > findleaks: elapsed wall time => 15 seconds > findleaks: > CACHE LEAKED BUFCTL CALLER > ---------------------------------------------------------------------- > Total 0 buffers, 0 bytes
That certainly doesn't look like a leak. It's time to go diving into ::kmausers and the other kmem-related information to find out what's going on. If this happens shortly after system boot, I wouldn't be too concerned. But if it's a persistent state, then I suspect something odd is going on. -- James Carlson 42.703N 71.076W <carls...@workingcode.com> _______________________________________________ networking-discuss mailing list networking-discuss@opensolaris.org
