> What is not clear to me is why you seem to be focusing on the GLDv3 code > path when you are disabling a common optimization done by existing DLPI > drivers. It seems that doing an analysis of the lack of that > optimization and its performance impact would be a useful step to take > before revisiting the GLDv3 code path.
The data we obtained from the Sun Analyzer tools made it very clear that most of the receive time is spent in the GLDv3 codepaths -- and that overhead will be there regardless of the driver optimizations, no? -- meem
