summaryrefslogtreecommitdiffstats
path: root/drivers/net/cxgb3/cxgb3_offload.h
diff options
context:
space:
mode:
authorFrederic Weisbecker <fweisbec@gmail.com>2009-07-02 17:58:19 +0200
committerIngo Molnar <mingo@elte.hu>2009-07-02 20:47:14 +0200
commit14f4654cbd531d48651e005cf05907c14bddb193 (patch)
tree4b94148c21e90705a188523174ee2c21e81151ca /drivers/net/cxgb3/cxgb3_offload.h
parent429764873cf3fc3e73142872a674bb27cda589c1 (diff)
downloadop-kernel-dev-14f4654cbd531d48651e005cf05907c14bddb193.zip
op-kernel-dev-14f4654cbd531d48651e005cf05907c14bddb193.tar.gz
perf_counter tools: Create new chain_for_each_child() iterator
Iterating through children of a node in the callchain tree shows something that may be quite confusing at a first glance. The head is the children field of the parent and the list nodes are in the brothers field of the children. This is because the childs are linked to the parent as a list of "brothers" using the "children" list of the parent as a head: --------------- | Parent (head) |------------------------------------- --------------- | | | children | | | ----------- ----------- | | 1st child |---brother---| 2nd child |---brother----- ----------- ----------- This makes the following strange pattern often occuring: list_for_each_entry(child, &parent->children, brothers) { // do something with children } Abstract it to chain_for_each_child() to factorize and simplify this pattern. Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl> Cc: Mike Galbraith <efault@gmx.de> Cc: Paul Mackerras <paulus@samba.org> Cc: Anton Blanchard <anton@samba.org> Cc: Arnaldo Carvalho de Melo <acme@redhat.com> LKML-Reference: <1246550301-8954-1-git-send-email-fweisbec@gmail.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'drivers/net/cxgb3/cxgb3_offload.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud