[lkml]   [1997]   [Jan]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: writev() inefficiency
Linux will normally coallesce writev() in accordance with the protocol. It
always does this for UDP, and RAW sockets. For TCP you will see the same
but the data may be split according to Nagle and maximum fragment sizes

Old libc's emulate writev() rather than using the later kernel writev()
and this causes the behaviour you describe. Try again with 2.0.x and

 \ /
  Last update: 2005-03-22 13:38    [W:0.029 / U:1.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site