diff options
author | David Howells <dhowells@redhat.com> | 2016-09-23 12:39:23 +0100 |
---|---|---|
committer | David Howells <dhowells@redhat.com> | 2016-09-23 13:23:09 +0100 |
commit | 9aff212bd677829189fae2e2e408cefc196ae5ae (patch) | |
tree | 9f042ceba0cb1ff2ab30400fa5f0b474e7ff5c31 | |
parent | b24d2891cfb0a7975b0039743439c98fe7b7dea7 (diff) | |
download | linux-9aff212bd677829189fae2e2e408cefc196ae5ae.tar.bz2 |
rxrpc: Don't send an ACK at the end of service call response transmission
Don't send an IDLE ACK at the end of the transmission of the response to a
service call. The service end resends DATA packets until the client sends an
ACK that hard-acks all the send data. At that point, the call is complete.
Signed-off-by: David Howells <dhowells@redhat.com>
-rw-r--r-- | net/rxrpc/recvmsg.c | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/net/rxrpc/recvmsg.c b/net/rxrpc/recvmsg.c index 6ba4af5a8d95..99e4c0ae30f1 100644 --- a/net/rxrpc/recvmsg.c +++ b/net/rxrpc/recvmsg.c @@ -143,8 +143,6 @@ static void rxrpc_end_rx_phase(struct rxrpc_call *call) if (call->state == RXRPC_CALL_CLIENT_RECV_REPLY) { rxrpc_propose_ACK(call, RXRPC_ACK_IDLE, 0, 0, true, false); rxrpc_send_call_packet(call, RXRPC_PACKET_TYPE_ACK); - } else { - rxrpc_propose_ACK(call, RXRPC_ACK_IDLE, 0, 0, false, false); } write_lock_bh(&call->state_lock); |