summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorPoddar, Siddarth <siddpodd@codeaurora.org>2017-03-19 16:10:48 +0530
committerPoddar, Siddarth <siddpodd@codeaurora.org>2017-03-19 16:18:44 +0530
commit78a7d50d7c43005e816c19500e98fac68d3884a7 (patch)
treec1bbf4d4a614858ac0a1e7120cf180e2d611fafc /tools/perf/scripts/python
parentbe0cf80d3a2d30d52668efa83c7b4ba6ef0441d7 (diff)
qcacmn: Add a flag in skb->cb for packet tracking
When a packet is generated internally, host adds a debug node entry to the table and deletes the entry once received tx completion for that packet by calling qdf_nbuf_free. But when a packet is coming from network stack, host doesn’t add any debug entry to the table and on receiving tx completion, it calls qdf_nbuf_tx_free which will simply free the skb. In case of P2P GO mode where packets are forwarded internally, host creates a private copy of skb and add debug node entry in the table. But when receiving a tx completion for the same packet host calls qdf_nbuf_tx_free which will free the skb but will not remove this node entry from the table. Currently, this api is common for all data tx completion packets. Add an extra flag in control block to differentiate whether skb is generated by driver or come from network stack. If flag is true, that means generated internally and need to remove the entry from debug node table. Change-Id: I61a76fdfedf0429e1b972824dc4513065d53033f CRs-Fixed: 2020947
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions