summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorBenjamin Herrenschmidt <benh@kernel.crashing.org>2017-04-06 11:02:45 +1000
committerDavid S. Miller <davem@davemloft.net>2017-04-06 15:39:45 -0700
commitd72e01a0430f8a1ae7adb3cbf0b2e73fcd99252e (patch)
tree14e9d4bc90f89704122ac9400acb3587cf48e2c3 /tools/perf/scripts/python/call-graph-from-postgresql.py
parentb1977bfbca569426651ac47e0f99d279f00f8a94 (diff)
ftgmac100: Use a scratch buffer for failed RX allocations
We can occasionally fail to allocate new RX buffers at runtime or when starting the driver. At the moment the latter just fails to open which is fine but the former leaves stale DMA pointers in the ring. Instead, use a scratch page and have all RX ring descriptors point to it by default unless a proper buffer can be allocated. It will help later on when re-initializing the whole ring at runtime on link changes since there is no clean failure path there unlike open(). Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions