Changes between Initial Version and Version 1 of Ticket #8733


Ignore:
Timestamp:
Feb 4, 2014 5:43:19 AM (16 months ago)
Author:
tibbe
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #8733 – Description

    initial v1  
    1 Network applications often call send followed by recv, to send a message and then read an answer. This causes syscall traces like this one: 
     1Network applications often call `send` followed by `recv`, to send a message and then read an answer. This causes syscall traces like this one: 
    22 
    33{{{ 
     
    1212}}} 
    1313 
    14 The recvfrom call always fails, as the response from the partner we're communicating with won't be available right after we send the request. 
     14The `recvfrom` call always fails, as the response from the partner we're communicating with won't be available right after we send the request. 
    1515 
    1616We ought to consider descheduling the thread as soon as sending is "done". The hard part is to figure out when that is.