From: P@draigBrady.com
To: Harald Welte <laforge@netfilter.org>
Cc: Peteris Krumins <newsgroups@lf.lv>, netfilter-devel@lists.netfilter.org
Subject: Re: performance
Date: Thu, 12 Jun 2003 13:04:23 +0100 [thread overview]
Message-ID: <3EE86C47.7030204@draigBrady.com> (raw)
In-Reply-To: <20030611121611.GM32593@sunbeam.de.gnumonks.org>
Harald Welte wrote:
> In order to get any idea about how those clock ticks are distributed
> among the various pars of kernel networking, you need to use some means
> of profiling.
iptables is in modules so I can't profile it at the moment.
But this is informative. This is with 160 match any rules in the
mangle::PREROUTING chain and then the packets are just dropped after.
Packet rate again is 85Kpps.
14754 total 0.0096
11421 default_idle 142.7625 (71% !!)
537 handle_IRQ_event 3.3563
341 eth_type_trans 1.7760
298 ip_rcv 0.4233
238 do_gettimeofday 1.8594
224 netif_rx 0.5185
217 add_timer_randomness 0.9042
196 skb_release_data 1.3611
180 batch_entropy_store 1.0227
162 alloc_skb 0.3375
157 process_backlog 0.5164
137 kfree 0.7784
126 __kmem_cache_alloc 0.3937
109 netif_receive_skb 0.2004
85 nf_hook_slow 0.1771
66 kmalloc 0.8250
61 kfree_skbmem 0.4766
50 __constant_c_and_count_memset 0.3125
36 __kfree_skb 0.0978
28 nf_iterate 0.1750
16 get_sample_stats 0.1250
15 add_entropy_words 0.0852
14 ip_promisc_rcv_finish 0.2917
10 kmem_cache_free 0.0625
8 add_interrupt_randomness 0.1250
6 __generic_copy_to_user 0.0625
4 schedule 0.0030
2 net_rx_action 0.0057
2 do_softirq 0.0089
The main question is why all the idle time?
Note userspace is locked out at this packet rate.
system specs:
dual 1.4GHz PIII
e1000 nic
kernel 2.4.20
Pádraig.
next prev parent reply other threads:[~2003-06-12 12:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 16:12 performance P
2003-06-09 16:16 ` performance P
2003-06-09 18:27 ` Re[2]: performance Peteris Krumins
2003-06-10 8:49 ` performance P
2003-06-11 12:16 ` performance Harald Welte
2003-06-12 12:04 ` P [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-07 16:36 Performance erik.teose
2003-03-07 7:48 Performance Aman
2002-08-02 6:55 Max IO size Mukul Kotwani
2002-08-02 7:50 ` Performance Mukul Kotwani
2002-08-02 9:16 ` Performance Fabien Salvi
2002-08-02 14:16 ` Performance Craig Tierney
2002-08-02 23:01 ` Performance Mukul Kotwani
2002-08-02 23:06 ` Performance Randy.Dunlap
2002-08-03 8:26 ` Performance Mukul Kotwani
2002-08-03 16:34 ` Performance Randy.Dunlap
2002-08-03 18:16 ` Performance Simon Trimmer
2002-08-03 20:03 ` Performance Mukul Kotwani
2002-08-04 6:27 ` Performance Jeremy Higdon
2002-08-04 7:39 ` Performance Mukul Kotwani
2002-08-04 8:01 ` Performance Jeremy Higdon
2002-04-22 15:15 Performance Gregor Pavlin
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=3EE86C47.7030204@draigBrady.com \
--to=p@draigbrady.com \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=newsgroups@lf.lv \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.