s390/qeth: don't replace a fully completed async TX buffer
authorJulian Wiedmann <jwi@linux.ibm.com>
Mon, 7 Dec 2020 13:12:31 +0000 (14:12 +0100)
committerDavid S. Miller <davem@davemloft.net>
Mon, 7 Dec 2020 14:55:21 +0000 (06:55 -0800)
commitdb4ffdcef7c9a842e55228c9faef7abf8b72382f
treecc083f8affab2d6316293d4826bad5657e195c03
parent0b8da8110b4fa3314a060e5c5a3b35a22b81e900
s390/qeth: don't replace a fully completed async TX buffer

For TX buffers that require an additional async notification via QAOB, the
TX completion code can now manage all the necessary processing if the
notification has already occurred (or is occurring concurrently).

In such cases we can avoid replacing the metadata that is associated
with the buffer's slot on the ring, and just keep using the current one.

As qeth_clear_output_buffer() will also handle any kmem cache-allocated
memory that was mapped into the TX buffer, qeth_qdio_handle_aob()
doesn't need to worry about it.

While at it, also remove the unneeded forward declaration for
qeth_init_qdio_out_buf().

Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
drivers/s390/net/qeth_core_main.c