Searched hist:"84 e28aa5" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/include/trace/events/ |
| H A D | rxrpc.h | 84e28aa5 Mon Oct 17 04:55:41 CDT 2022 David Howells <dhowells@redhat.com> rxrpc: Generate extra pings for RTT during heavy-receive call
When doing a call that has a single transmitted data packet and a massive
amount of received data packets, we only ping for one RTT sample, which
means we don't get a good reading on it.
Fix this by converting occasional IDLE ACKs into PING ACKs to elicit a
response.
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Marc Dionne <marc.dionne@auristor.com>
cc: linux-afs@lists.infradead.org
|
| /openbmc/linux/net/rxrpc/ |
| H A D | call_event.c | 84e28aa5 Mon Oct 17 04:55:41 CDT 2022 David Howells <dhowells@redhat.com> rxrpc: Generate extra pings for RTT during heavy-receive call
When doing a call that has a single transmitted data packet and a massive
amount of received data packets, we only ping for one RTT sample, which
means we don't get a good reading on it.
Fix this by converting occasional IDLE ACKs into PING ACKs to elicit a
response.
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Marc Dionne <marc.dionne@auristor.com>
cc: linux-afs@lists.infradead.org
|
| H A D | output.c | 84e28aa5 Mon Oct 17 04:55:41 CDT 2022 David Howells <dhowells@redhat.com> rxrpc: Generate extra pings for RTT during heavy-receive call
When doing a call that has a single transmitted data packet and a massive
amount of received data packets, we only ping for one RTT sample, which
means we don't get a good reading on it.
Fix this by converting occasional IDLE ACKs into PING ACKs to elicit a
response.
Signed-off-by: David Howells <dhowells@redhat.com>
cc: Marc Dionne <marc.dionne@auristor.com>
cc: linux-afs@lists.infradead.org
|