I'm filing this as self sponsored fast track. This case seeks minor binding; there are no plans to backport it to an update release. As the nature of this case is extremely straight forward, it is being submitted as an automatic, closed, case.
Problem ------- Looking at ipnet, there is no instrumentation to tell an observer about how it is functioning. No statistics are available about whether or not it runs out of buffers, how many packets get accepted vs rejected, etc. Proposal -------- This document proposes to add kstats to ipnet to provide statistics about how the ipnet module is performing. The statistics proposed at this stage are will be provided per stack instance and will be visible inside the respective zone. duplicationFail - packet duplicate prior to dispatch failed dispatchOk - ddi_dispatch succeeded dispatchFail - ddi_dispatch failed dispatchHeaderDrop - ipnet_addheader caused packet to be dropped dispatchPutDrop - packet dropped: cannot put packet on queue dispatchDupDrop - packet dropped: copymsg/dupmsg fail in ipnet_dispatch dispatchDeliver - packet delivered with putnext/putq acceptOk - accept packet filter function wants the packet acceptFail - accept packet filter function rejects the packet The statistics will be local to each zone with its own stack instance. These kstats will be delivered under module "ipnet", name "ipnet_stats" and class "misc". All of the interfaces being introduced are uncommitted.
