diff options
| author | David Howells <dhowells@redhat.com> | 2016-09-24 18:05:27 +0100 |
|---|---|---|
| committer | David Howells <dhowells@redhat.com> | 2016-09-24 23:49:46 +0100 |
| commit | 0d967960d39ee89f9e0289692e9f7232f490e55c (patch) | |
| tree | 043b35c0ef2f2367018bb42ebfd2ab5b65c1e7cd /net/rxrpc/call_object.c | |
| parent | 31a1b989508ce64e8ead504884ced01e61870852 (diff) | |
| download | talos-obmc-linux-0d967960d39ee89f9e0289692e9f7232f490e55c.tar.gz talos-obmc-linux-0d967960d39ee89f9e0289692e9f7232f490e55c.zip | |
rxrpc: Schedule an ACK if the reply to a client call appears overdue
If we've sent all the request data in a client call but haven't seen any
sign of the reply data yet, schedule an ACK to be sent to the server to
find out if the reply data got lost.
If the server hasn't yet hard-ACK'd the request data, we send a PING ACK to
demand a response to find out whether we need to retransmit.
If the server says it has received all of the data, we send an IDLE ACK to
tell the server that we haven't received anything in the receive phase as
yet.
To make this work, a non-immediate PING ACK must carry a delay. I've chosen
the same as the IDLE ACK for the moment.
Signed-off-by: David Howells <dhowells@redhat.com>
Diffstat (limited to 'net/rxrpc/call_object.c')
0 files changed, 0 insertions, 0 deletions
