[lkml]   [2013]   [Feb]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/1] VSOCK: Introduce VM Sockets
Hi Gerd,

> > + written = transport->stream_enqueue(
> > + vsk, msg->msg_iov,
> > + len - total_written);
> Hmm, shouldn't we pass total_written to stream_enqueue here?
> In case a blocking send(big-buffer) call gets splitted into multiple
> stream_enqueue calls the second (and further) stream_enqueue calls need
> to know at which msg offset they should continue sending the data, no?

On the client side, the iov tracks it internally; see memcpy_fromiovec().
On the socket side, VMCI uses a ring buffer, so it also knows its
position internally. Or did I misunderstand the question?

- Andy

 \ /
  Last update: 2013-02-18 18:21    [W:0.253 / U:0.032 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site