> I think it's overkill here since xesballoc() is only supposed to be > consolidation private but I have no problem with the mblk_t being passed > as an argument. I'll modify my prototype code accordingly.
"Supposed to be" being the key bit; STREAMS message allocation routines have a track record of escape, and I suspect this one will be no different if it improves performance. In any case, having the additional argument addresses the concern. -- meem
