Searched hist:"5 d39dc21482aad384d0a34f44cd06cb841a9ee29" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/drivers/net/ethernet/freescale/dpaa2/ |
| H A D | dpaa2-eth.h | diff 5d39dc21482aad384d0a34f44cd06cb841a9ee29 Mon Nov 26 10:27:31 CST 2018 Ioana Ciocoi Radulescu <ruxandra.radulescu@nxp.com> dpaa2-eth: Release buffers back to pool on XDP_DROP
Instead of freeing the RX buffers, release them back into the pool.
We wait for the maximum number of buffers supported by a single
release command to accumulate before issuing the command.
Also, don't unmap the Rx buffers at the beginning of the Rx routine
anymore, since that would require remapping them before release.
Instead, just do a DMA sync at first and only unmap if the frame is
meant for the stack.
Signed-off-by: Ioana Radulescu <ruxandra.radulescu@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | dpaa2-eth.c | diff 5d39dc21482aad384d0a34f44cd06cb841a9ee29 Mon Nov 26 10:27:31 CST 2018 Ioana Ciocoi Radulescu <ruxandra.radulescu@nxp.com> dpaa2-eth: Release buffers back to pool on XDP_DROP
Instead of freeing the RX buffers, release them back into the pool.
We wait for the maximum number of buffers supported by a single
release command to accumulate before issuing the command.
Also, don't unmap the Rx buffers at the beginning of the Rx routine
anymore, since that would require remapping them before release.
Instead, just do a DMA sync at first and only unmap if the frame is
meant for the stack.
Signed-off-by: Ioana Radulescu <ruxandra.radulescu@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|