Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 25 Jan 2008 14:03:20 +0200
From:      Stefan Lambrev <stefan.lambrev@moneybookers.com>
To:        freebsd-pf@freebsd.org
Subject:   Re: PF makes em0 taskq to eat 100% CPU
Message-ID:  <4799D008.8020201@moneybookers.com>
In-Reply-To: <4798B13D.4080701@moneybookers.com>
References:  <4798B13D.4080701@moneybookers.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Greets,

Thanks to Kris Kennaway I was able to get pmc profiling working,
Here is the "top" while flooding target behind the firewall:

  %   cumulative   self              self     total
 time   seconds   seconds    calls  ms/call  ms/call  name
 24.4  231689.00 231689.00        0  100.00%           _mtx_lock_sleep [1]
  6.5  293004.00 61315.00        0  100.00%           
pf_state_compare_ext_gwy [2]
  6.4  353672.00 60668.00        0  100.00%           pf_src_compare [3]
  3.8  389565.00 35893.00        0  100.00%           
pf_state_compare_lan_ext [4]
  3.5  422911.00 33346.00        0  100.00%           pf_test [5]
  3.2  453703.00 30792.00        0  100.00%           bcopy [6]
  2.9  481264.00 27561.00        0  100.00%           pf_test_tcp [7]
  2.1  501546.00 20282.00        0  100.00%           pfsync_pack_state [8]
  2.0  520685.00 19139.00        0  100.00%           
pf_state_compare_id [9]
  2.0  539293.00 18608.00        0  100.00%           bridge_pfil [10]
  1.6  554228.00 14935.00        0  100.00%           uma_zfree_arg [11]
  1.5  568593.00 14365.00        0  100.00%           uma_zalloc_arg [12]
  1.4  581556.00 12963.00        0  100.00%           bzero [13]
  1.2  592594.00 11038.00        0  100.00%           
bus_dmamap_load_mbuf_sg [14]
  1.1  603052.00 10458.00        0  100.00%           
bridge_rtnode_lookup [15]
  1.1  613173.50 10121.50        0  100.00%           _rw_rlock [16]
  1.0  622984.50  9811.00        0  100.00%           rn_match [17]
  1.0  632477.00  9492.50        0  100.00%           
pf_state_tree_id_RB_REMOVE [18]
  0.9  641356.00  8879.00        0  100.00%           bridge_forward [19]
  0.9  649984.00  8628.00        0  100.00%           em_encap [20]
  0.9  658479.00  8495.00        0  100.00%           _rw_runlock [21]

So the kernel spend 24.4% waiting for _mtx_lock_sleep .. I think 
something is really wrong here.
I'll make profiling with polling enabled on network interfaces.

-- 

Best Wishes,
Stefan Lambrev
ICQ# 24134177




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4799D008.8020201>