You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(I realize syscall has moved to its own repo as of 1.4, but that repo doesn't have a bug tracker so I assume this is still the right place to file such things, please correct me if I'm wrong.)
The unix Sendmsg and SendmsgN system calls permit passing in multiple buffers through the use of an io-vector structure, however the Go wrappers for these functions take only a single []byte and hard-code the length of the io-vector to 1. It would be very useful for performance in some cases (such as IBM/sarama#238) if Sendmsg could be made to take a [][]byte and construct the equivalent io-vector.
The text was updated successfully, but these errors were encountered:
minux
changed the title
syscall: sendmsg does not permit sending multiple buffers
sys/unix: sendmsg does not permit sending multiple buffers
Dec 19, 2014
GIven the existence of net.Buffers, perhaps we can do something along the lines of SendmsgBuffers. Not that we should import "net", but we could add a Buffers type to x/sys/unix. I'm not quite sure that makes sense, though.
(I realize syscall has moved to its own repo as of 1.4, but that repo doesn't have a bug tracker so I assume this is still the right place to file such things, please correct me if I'm wrong.)
The unix
Sendmsg
andSendmsgN
system calls permit passing in multiple buffers through the use of an io-vector structure, however the Go wrappers for these functions take only a single[]byte
and hard-code the length of the io-vector to 1. It would be very useful for performance in some cases (such as IBM/sarama#238) ifSendmsg
could be made to take a[][]byte
and construct the equivalent io-vector.The text was updated successfully, but these errors were encountered: