Searched hist:"805 b21b9" (Results 1 – 4 of 4) sorted by relevance
/openbmc/linux/net/rxrpc/ |
H A D | misc.c | 805b21b9 Sat Sep 24 12:05:26 CDT 2016 David Howells <dhowells@redhat.com> rxrpc: Send an ACK after every few DATA packets we receive
Send an ACK if we haven't sent one for the last two packets we've received. This keeps the other end apprised of where we've got to - which is important if they're doing slow-start.
We do this in recvmsg so that we can dispatch a packet directly without the need to wake up the background thread.
This should possibly be made configurable in future.
Signed-off-by: David Howells <dhowells@redhat.com> 805b21b9 Sat Sep 24 12:05:26 CDT 2016 David Howells <dhowells@redhat.com> rxrpc: Send an ACK after every few DATA packets we receive Send an ACK if we haven't sent one for the last two packets we've received. This keeps the other end apprised of where we've got to - which is important if they're doing slow-start. We do this in recvmsg so that we can dispatch a packet directly without the need to wake up the background thread. This should possibly be made configurable in future. Signed-off-by: David Howells <dhowells@redhat.com>
|
H A D | recvmsg.c | 805b21b9 Sat Sep 24 12:05:26 CDT 2016 David Howells <dhowells@redhat.com> rxrpc: Send an ACK after every few DATA packets we receive
Send an ACK if we haven't sent one for the last two packets we've received. This keeps the other end apprised of where we've got to - which is important if they're doing slow-start.
We do this in recvmsg so that we can dispatch a packet directly without the need to wake up the background thread.
This should possibly be made configurable in future.
Signed-off-by: David Howells <dhowells@redhat.com> 805b21b9 Sat Sep 24 12:05:26 CDT 2016 David Howells <dhowells@redhat.com> rxrpc: Send an ACK after every few DATA packets we receive Send an ACK if we haven't sent one for the last two packets we've received. This keeps the other end apprised of where we've got to - which is important if they're doing slow-start. We do this in recvmsg so that we can dispatch a packet directly without the need to wake up the background thread. This should possibly be made configurable in future. Signed-off-by: David Howells <dhowells@redhat.com>
|
H A D | output.c | 805b21b9 Sat Sep 24 12:05:26 CDT 2016 David Howells <dhowells@redhat.com> rxrpc: Send an ACK after every few DATA packets we receive
Send an ACK if we haven't sent one for the last two packets we've received. This keeps the other end apprised of where we've got to - which is important if they're doing slow-start.
We do this in recvmsg so that we can dispatch a packet directly without the need to wake up the background thread.
This should possibly be made configurable in future.
Signed-off-by: David Howells <dhowells@redhat.com> 805b21b9 Sat Sep 24 12:05:26 CDT 2016 David Howells <dhowells@redhat.com> rxrpc: Send an ACK after every few DATA packets we receive Send an ACK if we haven't sent one for the last two packets we've received. This keeps the other end apprised of where we've got to - which is important if they're doing slow-start. We do this in recvmsg so that we can dispatch a packet directly without the need to wake up the background thread. This should possibly be made configurable in future. Signed-off-by: David Howells <dhowells@redhat.com>
|
H A D | ar-internal.h | 805b21b9 Sat Sep 24 12:05:26 CDT 2016 David Howells <dhowells@redhat.com> rxrpc: Send an ACK after every few DATA packets we receive
Send an ACK if we haven't sent one for the last two packets we've received. This keeps the other end apprised of where we've got to - which is important if they're doing slow-start.
We do this in recvmsg so that we can dispatch a packet directly without the need to wake up the background thread.
This should possibly be made configurable in future.
Signed-off-by: David Howells <dhowells@redhat.com> 805b21b9 Sat Sep 24 12:05:26 CDT 2016 David Howells <dhowells@redhat.com> rxrpc: Send an ACK after every few DATA packets we receive Send an ACK if we haven't sent one for the last two packets we've received. This keeps the other end apprised of where we've got to - which is important if they're doing slow-start. We do this in recvmsg so that we can dispatch a packet directly without the need to wake up the background thread. This should possibly be made configurable in future. Signed-off-by: David Howells <dhowells@redhat.com>
|