aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorMichael Chan <mchan@broadcom.com>2016-01-02 23:44:59 -0500
committerDavid S. Miller <davem@davemloft.net>2016-01-04 15:54:39 -0500
commitb6ab4b01f53b5f9e17dbd4f91c95fa5049fa2101 (patch)
treee960e535b043cf6b4469f050b526e6c4194ac82e /tools/perf/scripts/python/call-graph-from-postgresql.py
parentbnxt_en: Refactor bnxt_dbg_dump_states(). (diff)
downloadlinux-dev-b6ab4b01f53b5f9e17dbd4f91c95fa5049fa2101.tar.xz
linux-dev-b6ab4b01f53b5f9e17dbd4f91c95fa5049fa2101.zip
bnxt_en: Separate bnxt_{rx|tx}_ring_info structs from bnxt_napi struct.
Currently, an rx and a tx ring are always paired with a completion ring. We want to restructure it so that it is possible to have a dedicated completion ring for tx or rx only. The bnxt hardware uses a completion ring for rx and tx events. The driver has to process the completion ring entries sequentially for the rx and tx events. Using a dedicated completion ring for rx only or tx only has these benefits: 1. A burst of rx packets can cause delay in processing tx events if the completion ring is shared. If tx queue is stopped by BQL, this can cause delay in re-starting the tx queue. 2. A completion ring is sized according to the rx and tx ring size rounded up to the nearest power of 2. When the completion ring is shared, it is sized by adding the rx and tx ring sizes and then rounded to the next power of 2, often with a lot of wasted space. 3. Using dedicated completion ring, we can adjust the tx and rx coalescing parameters independently for rx and tx. The first step is to separate the rx and tx ring structures from the bnxt_napi struct. In this patch, an rx ring and a tx ring will point to the same bnxt_napi struct to share the same completion ring. No change in ring assignment and mapping yet. Signed-off-by: Michael Chan <mchan@broadcom.com> 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