From: Radu Rendec <radu.rendec@ines.ro>
To: Jesper Dangaard Brouer <hawk@diku.dk>
Cc: Jarek Poplawski <jarkao2@gmail.com>,
Denys Fedoryschenko <denys@visp.net.lb>,
netdev <netdev@vger.kernel.org>
Subject: Re: htb parallelism on multi-core platforms
Date: Wed, 29 Apr 2009 13:21:34 +0300 [thread overview]
Message-ID: <1241000494.6554.307.camel@blade.ines.ro> (raw)
In-Reply-To: <Pine.LNX.4.64.0904281142270.21301@tyr.diku.dk>
Thanks for the oprofile newbie guide - it saved much time and digging
through man pages.
Normal report looks like this:
samples % image name app name symbol name
38424 30.7350 cls_u32.ko cls_u32 u32_classify
5321 4.2562 e1000e.ko e1000e e1000_clean_rx_irq
4690 3.7515 vmlinux vmlinux ipt_do_table
3825 3.0596 sch_htb.ko sch_htb htb_dequeue
3458 2.7660 vmlinux vmlinux __hash_conntrack
2597 2.0773 vmlinux vmlinux nf_nat_setup_info
2531 2.0245 vmlinux vmlinux kmem_cache_alloc
2229 1.7830 vmlinux vmlinux ip_route_input
1722 1.3774 vmlinux vmlinux nf_conntrack_in
1547 1.2374 sch_htb.ko sch_htb htb_enqueue
1519 1.2150 vmlinux vmlinux kmem_cache_free
1471 1.1766 vmlinux vmlinux __slab_free
1435 1.1478 vmlinux vmlinux dev_queue_xmit
1313 1.0503 vmlinux vmlinux __qdisc_run
1277 1.0215 vmlinux vmlinux netif_receive_skb
All other symbols are below 1%.
sch_htb.ko report is this:
samples % image name symbol name
-------------------------------------------------------------------------------
3825 49.0762 sch_htb.ko htb_dequeue
3825 100.000 sch_htb.ko htb_dequeue [self]
-------------------------------------------------------------------------------
1547 19.8486 sch_htb.ko htb_enqueue
1547 100.000 sch_htb.ko htb_enqueue [self]
-------------------------------------------------------------------------------
608 7.8009 sch_htb.ko htb_lookup_leaf
608 100.000 sch_htb.ko htb_lookup_leaf [self]
-------------------------------------------------------------------------------
459 5.8891 sch_htb.ko htb_deactivate_prios
459 100.000 sch_htb.ko htb_deactivate_prios [self]
-------------------------------------------------------------------------------
417 5.3503 sch_htb.ko htb_add_to_wait_tree
417 100.000 sch_htb.ko htb_add_to_wait_tree [self]
-------------------------------------------------------------------------------
372 4.7729 sch_htb.ko htb_change_class_mode
372 100.000 sch_htb.ko htb_change_class_mode [self]
-------------------------------------------------------------------------------
276 3.5412 sch_htb.ko htb_activate_prios
276 100.000 sch_htb.ko htb_activate_prios [self]
-------------------------------------------------------------------------------
189 2.4249 sch_htb.ko htb_add_to_id_tree
189 100.000 sch_htb.ko htb_add_to_id_tree [self]
-------------------------------------------------------------------------------
101 1.2959 sch_htb.ko htb_safe_rb_erase
101 100.000 sch_htb.ko htb_safe_rb_erase [self]
-------------------------------------------------------------------------------
Am I misinterpreting the results, or does it look like the real problem
is actually packet classification?
Thanks,
Radu Rendec
On Tue, 2009-04-28 at 12:15 +0200, Jesper Dangaard Brouer wrote:
> Remember to keep/copy the file "vmlinux".
>
> Here is the steps I usually use:
>
> opcontrol --vmlinux=/boot/vmlinux-`uname -r`
>
> opcontrol --stop
> opcontrol --reset
> opcontrol --start
>
> <perform stuff that needs profiling>
>
> opcontrol --stop
>
> "Normal" report
> opreport --symbols --image-path=/lib/modules/`uname -r`/kernel/ | less
>
> Looking at specific module "sch_htb"
>
> opreport --symbols -cl sch_htb.ko --image-path=/lib/modules/`uname
> -r`/kernel/
next prev parent reply other threads:[~2009-04-29 10:21 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 10:40 htb parallelism on multi-core platforms Radu Rendec
2009-04-17 11:31 ` David Miller
2009-04-17 11:33 ` Badalian Vyacheslav
2009-04-17 22:41 ` Jarek Poplawski
2009-04-18 0:21 ` Denys Fedoryschenko
2009-04-18 7:56 ` Jarek Poplawski
2009-04-22 14:02 ` Radu Rendec
2009-04-22 21:29 ` Jesper Dangaard Brouer
2009-04-23 8:20 ` Jarek Poplawski
2009-04-23 13:56 ` Radu Rendec
2009-04-23 18:19 ` Jarek Poplawski
2009-04-23 20:19 ` Jesper Dangaard Brouer
2009-04-24 9:42 ` Radu Rendec
2009-04-28 10:15 ` Jesper Dangaard Brouer
2009-04-29 10:21 ` Radu Rendec [this message]
2009-04-29 10:31 ` Jesper Dangaard Brouer
2009-04-29 11:03 ` Radu Rendec
2009-04-29 12:23 ` Jarek Poplawski
2009-04-29 13:15 ` Radu Rendec
2009-04-29 13:38 ` Jarek Poplawski
2009-04-29 16:21 ` Radu Rendec
2009-04-29 22:49 ` Calin Velea
2009-04-29 23:00 ` Re[2]: " Calin Velea
2009-04-30 11:19 ` Radu Rendec
2009-04-30 11:44 ` Jesper Dangaard Brouer
2009-04-30 14:04 ` Re[2]: " Calin Velea
2009-05-08 10:15 ` Paweł Staszewski
2009-05-08 17:55 ` Vladimir Ivashchenko
2009-05-08 18:07 ` Denys Fedoryschenko
2009-04-23 12:31 ` Radu Rendec
2009-04-23 18:43 ` Jarek Poplawski
2009-04-23 19:06 ` Jesper Dangaard Brouer
2009-04-23 19:14 ` Jarek Poplawski
2009-04-23 19:47 ` Jesper Dangaard Brouer
2009-04-23 20:00 ` Jarek Poplawski
2009-04-23 20:09 ` Jeff King
2009-04-24 6:01 ` Jarek Poplawski
[not found] ` <1039493214.20090424135024@gemenii.ro>
2009-04-24 11:19 ` Jarek Poplawski
2009-04-24 11:35 ` Re[2]: " Calin Velea
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1241000494.6554.307.camel@blade.ines.ro \
--to=radu.rendec@ines.ro \
--cc=denys@visp.net.lb \
--cc=hawk@diku.dk \
--cc=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).