Erik, In the design document, is the following:
"[If Volo could pass down the size of the message to the sendmsg function we could avoid msgdsize() all together.]"
Given the [], I'm not sure if this is an editorial mistake or not, but something that has been brought up a few times is expanding the mblk_t (or dblk_t?) to store a packet length and other useful information. Whilst the mblk_t is currently a nice multiple of system word size (and in some cases cache line size as well), micro-optimisation shouldn't be a design goal. With the above comment and the IP Refactoring project almost behind you now, what are your thoughts on allowing for this type of change?
Darren _______________________________________________ networking-discuss mailing list [email protected]
