David Howells bf7d620abf rxrpc: Don't request an ACK on the last DATA packet of a call's Tx phase ... Don't request an ACK on the last DATA packet of a call's Tx phase as for a client there will be a reply packet or some sort of ACK to shift phase. If the ACK is requested, OpenAFS sends a REQUESTED-ACK ACK with soft-ACKs in it and doesn't follow up with a hard-ACK. If we don't set the flag, OpenAFS will send a DELAY ACK that hard-ACKs the reply data, thereby allowing the call to terminate cleanly. Signed-off-by: David Howells <dhowells@redhat.com>		2016-10-06 08:11:51 +01:00
..
af_rxrpc.c
ar-internal.h	rxrpc: Need to produce an ACK for service op if op takes a long time	2016-10-06 08:11:50 +01:00
call_accept.c
call_event.c	rxrpc: Need to produce an ACK for service op if op takes a long time	2016-10-06 08:11:50 +01:00
call_object.c
conn_client.c
conn_event.c
conn_object.c
conn_service.c
input.c
insecure.c
Kconfig
key.c
local_event.c
local_object.c
Makefile
misc.c	rxrpc: Need to produce an ACK for service op if op takes a long time	2016-10-06 08:11:50 +01:00
output.c	rxrpc: Don't request an ACK on the last DATA packet of a call's Tx phase	2016-10-06 08:11:51 +01:00
peer_event.c
peer_object.c
proc.c
recvmsg.c	rxrpc: Need to produce an ACK for service op if op takes a long time	2016-10-06 08:11:50 +01:00
rxkad.c
security.c
sendmsg.c	rxrpc: Need to produce an ACK for service op if op takes a long time	2016-10-06 08:11:50 +01:00
skbuff.c
sysctl.c
utils.c