Oleksandr Samoylyk wrote:
Julian Elischer wrote:
Oleksandr Samoylyk wrote:
David DeSimone wrote:
Julian Elischer <[EMAIL PROTECTED]> wrote:
unfortunatly I've been totally ignoring this thread because it said
"trouble with em" in the topic..
If you'd said "trouble with mpd" then maybe I'd have looked earlier..
In the poster's defense, the only symptom that started this was this
info from ps:
PID USERNAME THR PRI NICE SIZE RES STATE C TIME WCPU
COMMAND
29 root 1 -68 - 0K 16K CPU5 5 196:41 100.00%
em0 taskq
So tracking it down to mpd has been a process of elimination in
figuring
out why packets absorb so much CPU.
Here is a result of profiling:
http://lists.freebsd.org/pipermail/freebsd-net/2008-May/017901.html
0.00 0.00 16/1643247 igmp_input [833]
0.03 0.01 614/1643247 icmp_input [272]
93.07 17.27 1642617/1643247 encap4_input [9]
[10] 49.8 93.10 17.27 1643247 rip_input [10]
14.26 0.88 600796/749987 _mtx_lock_sleep
[21]
0.16 1.70 1643863/1643863 raw_append [93]
0.00 0.24 36345/176995 _mtx_unlock_sleep
[114]
0.01 0.00 1643863/5117962 jailed [278]
0.00 0.00 1292/1843 m_copym [666]
0.00 0.00 676/8214484 m_freem [34]
50% of time in rip_input???
that's unexpected.. what is the traffic?
more than 20k pps
I mean, what KIND of traffic?
I'm surprised it 's calling rip_input().. why is it calling
encap4_input()? (which calls rip_input).. what is the IP protocol
of all these packets?
what does a small snippet of traffic show?
(tcpdump -i em0 -s0 -e -n -c 64)
I see no netgraph in the profile at all.
did you statically compile it all in at compile time? (you should if
you want to see it)
Tried both variants. Now not statically.
make sure it is static and that the netgraph nodes are all compiled
with -pg
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
