diff options
author | Netanel Belgazal <netanel@amazon.com> | 2017-06-23 11:21:54 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-06-23 14:15:09 -0400 |
commit | ad974baef2a17a170fe837ad19f10dcab63e9470 (patch) | |
tree | 5383d85c07d6b141e33409a477d230514793801f /kernel/latencytop.c | |
parent | e2eed0e307f671e37f3829dfec5dbb1fba826a15 (diff) | |
download | linux-ad974baef2a17a170fe837ad19f10dcab63e9470.tar.bz2 |
net: ena: add support for out of order rx buffers refill
ENA driver post Rx buffers through the Rx submission queue
for the ENA device to fill them with receive packets.
Each Rx buffer is marked with req_id in the Rx descriptor.
Newer ENA devices could consume the posted Rx buffer in out of order,
and as result the corresponding Rx completion queue will have Rx
completion descriptors with non contiguous req_id(s)
In this change the driver holds two rings.
The first ring (called free_rx_ids) is a mapping ring.
It holds all the unused request ids.
The values in this ring are from 0 to ring_size -1.
When the driver wants to allocate a new Rx buffer it uses the head of
free_rx_ids and uses it's value as the index for rx_buffer_info ring.
The req_id is also written to the Rx descriptor
Upon Rx completion,
The driver took the req_id from the completion descriptor and uses it
as index in rx_buffer_info.
The req_id is then return to the free_rx_ids ring.
This patch also adds statistics to inform when the driver receive out
of range or unused req_id.
Note:
free_rx_ids is only accessible from the napi handler, so no locking is
required
Signed-off-by: Netanel Belgazal <netanel@amazon.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'kernel/latencytop.c')
0 files changed, 0 insertions, 0 deletions