blocking on recv saves a copy op?
blocking on recv saves a copy op?
- Subject: blocking on recv saves a copy op?
- From: "Tim Dorcey" <email@hidden>
- Date: Thu, 23 Mar 2006 19:55:06 -0800
- Importance: Normal
I just upgraded my app from OpenTransport to BSD sockets + pthreads, and
found it easier than expected. Now, I am wondering about a basic aspect of
socket operation. If I wait on select (or kqueue event) to signal the
arrival of (UDP) data before calling recvfrom, is that going to cost an
extra memory copy, versus having the socket block on recvfrom?
On the face of it, it seems like giving the socket a destination buffer
before the data arrives might save a copy. Or, is there some internal copy
that must occur in any case that would be postponed until recvfrom is
called?
I know, I should look in Stevens. Just got back from 2 bookstores, both of
whom have it on backorder.
Tim
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden