zero-copy on tx side optimised to minimise number of user/kernel space transitions

This commit is contained in:
Martin Sustrik 2009-12-10 08:25:21 +01:00
parent 1c1dfb50f8
commit 72dacc3570

View File

@ -56,12 +56,18 @@ namespace zmq
// If we are able to fill whole buffer in a single go, let's // If we are able to fill whole buffer in a single go, let's
// use zero-copy. There's no disadvantage to it as we cannot // use zero-copy. There's no disadvantage to it as we cannot
// stuck multiple messages into the buffer anyway. // stuck multiple messages into the buffer anyway. Note that
// subsequent write(s) are non-blocking, thus each single
// write writes at most SO_SNDBUF bytes at once not depending
// on how large is the chunk returned from here.
// As a consequence, large messages being sent won't block
// other engines running in the same I/O thread for excessive
// amounts of time.
if (pos == 0 && to_write >= *size_) { if (pos == 0 && to_write >= *size_) {
*data_ = write_pos; *data_ = write_pos;
write_pos += *size_; write_pos += to_write;
to_write -= *size_; pos = to_write;
pos = *size_; to_write = 0;
break; break;
} }