diff options
author | David S. Miller <davem@davemloft.net> | 2018-11-14 08:51:28 -0800 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-11-14 08:51:28 -0800 |
commit | 6d5db6c37929cb0a84e64ba0590a74593e5ce3b8 (patch) | |
tree | 77fe8efb581cd6fb9b608dc9de60f68cef4f8b78 /drivers/nvdimm | |
parent | 15cef30974c5f8b256008beb62dcbf15792b77a9 (diff) | |
parent | bd3b5d462add1c703dd02a7a6f498a0f1bea9f4a (diff) |
Merge branch 'nfp-abm-track-all-Qdiscs'
Jakub Kicinski says:
====================
nfp: abm: track all Qdiscs
Our Qdisc offload so far has been very simplistic. We held
and array of marking thresholds and statistics sized to the
number of PF queues. This was sufficient since the only
configuration we supported was single layer of RED Qdiscs
(on top of MQ or not, but MQ isn't really about queuing).
As we move to add more Qdiscs it's time to actually try to
track the full Qdisc hierarchy. This allows us to make sure
our offloaded configuration reflects the SW path better.
We add graft notifications to MQ and RED (PRIO already sends
them) to allow drivers offloading those to learn how Qdiscs
are linked. MQ graft gives us the obvious advantage of being
able to track when Qdiscs are shared or moved. It seems
unlikely HW would offload RED's child Qdiscs but since the
behaviour would change based on linked child we should
stop offloading REDs with modified child. RED will also
handle the child differently during reconfig when limit
parameter is set - so we have to inform the drivers about
the limit, and have them reset the child state when
appropriate.
The NFP driver will now allocate a structure to track each
Qdisc and link it to its children. We will also maintain
a shadow copy of threshold settings - to save device writes
and make it easier to apply defaults when config is
re-evaluated.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/nvdimm')
0 files changed, 0 insertions, 0 deletions