Searched hist:"07 beb1651adcd324f4d91584d5cab75d5882a9c2" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/drivers/net/ethernet/freescale/dpaa2/ |
| H A D | dpaa2-eth-dcb.c | diff 07beb1651adcd324f4d91584d5cab75d5882a9c2 Sat May 30 16:08:14 CDT 2020 Ioana Ciornei <ioana.ciornei@nxp.com> dpaa2-eth: Keep congestion group taildrop enabled when PFC on
Leave congestion group taildrop enabled for all traffic classes
when PFC is enabled. Notification threshold is low enough such
that it will be hit first and this also ensures that FQs on
traffic classes which are not PFC enabled won't drain the buffer
pool.
FQ taildrop threshold is kept disabled as long as any form of
flow control is on. Since FQ taildrop works with bytes, not number
of frames, we can't guarantee it will not interfere with the
congestion notification mechanism for all frame sizes.
Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | dpaa2-eth.h | diff 07beb1651adcd324f4d91584d5cab75d5882a9c2 Sat May 30 16:08:14 CDT 2020 Ioana Ciornei <ioana.ciornei@nxp.com> dpaa2-eth: Keep congestion group taildrop enabled when PFC on
Leave congestion group taildrop enabled for all traffic classes
when PFC is enabled. Notification threshold is low enough such
that it will be hit first and this also ensures that FQs on
traffic classes which are not PFC enabled won't drain the buffer
pool.
FQ taildrop threshold is kept disabled as long as any form of
flow control is on. Since FQ taildrop works with bytes, not number
of frames, we can't guarantee it will not interfere with the
congestion notification mechanism for all frame sizes.
Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| H A D | dpaa2-eth.c | diff 07beb1651adcd324f4d91584d5cab75d5882a9c2 Sat May 30 16:08:14 CDT 2020 Ioana Ciornei <ioana.ciornei@nxp.com> dpaa2-eth: Keep congestion group taildrop enabled when PFC on
Leave congestion group taildrop enabled for all traffic classes
when PFC is enabled. Notification threshold is low enough such
that it will be hit first and this also ensures that FQs on
traffic classes which are not PFC enabled won't drain the buffer
pool.
FQ taildrop threshold is kept disabled as long as any form of
flow control is on. Since FQ taildrop works with bytes, not number
of frames, we can't guarantee it will not interfere with the
congestion notification mechanism for all frame sizes.
Signed-off-by: Ioana Ciornei <ioana.ciornei@nxp.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|