?? wrote: > Our question is: Is there an alternative path for "recvfrom" which is more > simple than the current sotpi_recvmsg imeplementation, and will not lock > during copying data from kernel to user space ?
I think the usual method in this scenario is just use select() on the socket. When there is something to be read, select() returns and your app can decide which one of those processes should handle this packet and then dispatch that packet to that process. And if all the processes are actually doing the same thing, you may also consider using threads instead. It is much more light weight. You may also consider using event ports. See port_create(3C), port_associate(3C) and port_get(3C). See also the following article for more info http://developers.sun.com/solaris/articles/event_completion.html -- K. Poon. kacheong.poon at sun.com
