RE: kernel profiling: spinlock_exit consumes 36% CPU time.

2008-10-08 Thread 邱剑
Forgot to meantion that the test is based on FreeBSD kernel 7.0 2000807 snapshot. The kernel was compiled with a modified version of GENERIC configuration. With SMP and PREEMPTION disabled and kernel profiling enabled. -Original Message- From: Jeremy Chadwick [mailto:[EMAIL PROTECTED] S

"route flush" does not delete routes created with -interface option

2008-10-08 Thread Johann Hugo
Is there a way to get rid of all the routes in a routing table ? This is more or less what I do: route add 146.64.80.0/24 192.168.0.100 route add 146.141.0.0 -interface tun1 route add 146.182.0.0 -interface tun1 route add 146.230.0.0 -interface tun1 netstat -rn inet 146.64.80.0/24 192.168.0.

Re: EM and TSO

2008-10-08 Thread Steven Hartland
Even on PCI-e devices this has some nasty side effects i.e. on a PFSence firewall box based on 7.0-RELEASE-p3 with TSO enabled, access via the public network to the web interface is almost impossible. Simply disabling TSO and all was good. This may not be strictly down to the HW or driver but is

em(4) status

2008-10-08 Thread H.fazaeli
Hi all and Jack Are the changes discussed in: http://lists.freebsd.org/pipermail/freebsd-net/2008-January/016584.html http://lists.freebsd.org/pipermail/freebsd-net/2007-August/014959.html incorporated into em(4)? If not, is there any near plans to do so? -- Best regards. Hooman Fazaeli <[

Re: kernel profiling: spinlock_exit consumes 36% CPU time.

2008-10-08 Thread John Baldwin
On Wednesday 08 October 2008 03:51:48 am 邱剑 wrote: > Many thanks for the information. > > Could we say that interrupt handlers consumed ~36% execution time? > > Is this number too high? Is it possible that we abuse the use of critical > sections in kernel? I think whether or not it is high depen

Re: kernel profiling: spinlock_exit consumes 36% CPU time.

2008-10-08 Thread Bruce Evans
On Tue, 7 Oct 2008, John Baldwin wrote: On Tuesday 07 October 2008 07:44:00 am wrote: Hi, folks, I did kernel profiling when a single thread client sends UDP packets to a single thread server on the same machine. In the output kernel profile, the first few kernel functions that consumes