Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 28 Jul 2014 10:51:11 -0400
From:      John Jasen <jjasen@gmail.com>
To:        Adrian Chadd <adrian@freebsd.org>
Cc:        FreeBSD Net <freebsd-net@freebsd.org>
Subject:   Re: fastforward/routing: a 3 million packet-per-second system?
Message-ID:  <CAACLuR09etiyujR7-qOGSUQpQFH1o6S38_96_uSd9Cy57OnYYQ@mail.gmail.com>
In-Reply-To: <CAJ-VmonMYi-7ZCw-PqiuOp5euAdxbyiHXW-ZW96MWQ8%2B-RV8MA@mail.gmail.com>
References:  <53CE80DD.9090109@gmail.com> <CAACLuR1r0axCYWXeLDSa-m07eAVgTMBVW5sNbt%2By_Lt2ss1r7Q@mail.gmail.com> <CAJ-Vmonsc79ULDOT9trtOotq7mRh1XJkhL2JfDNxXP16OFWMFg@mail.gmail.com> <CAJ-Vmok6vyrD-2%2BswCBPP_VeMqH6t7CXuVBPUaDfwyRrb6aiTg@mail.gmail.com> <53D4600A.1010505@gmail.com> <CAJ-Vmonf_krdxrkrKbjkC-a=4x0M7y9mXeTGMvs1qOSGNbqdGA@mail.gmail.com> <53D4F77B.9020009@gmail.com> <CAJ-VmonMYi-7ZCw-PqiuOp5euAdxbyiHXW-ZW96MWQ8%2B-RV8MA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
in_input crept up into the top 5, versus fastforward.


Would PMC counters help?

 cat debug.lock.pref.stats.out-20140728-1 | sort -nk 4 | tail -5
       5         4         413         115         160      2      0  0
63 /usr/src/sys/kern/kern_condvar.c:145 (sleep mutex:Giant)
       1         1      148858        4095      650072      0      0  0
 11184 /usr/src/sys/kern/subr_turnstile.c:552 (spin mutex:turnstile chain)
       8        14    13747639      561636    72520256      0      0  0
689603 /usr/src/sys/net/route.c:439 (sleep mutex:rtentry)
       3        20     3907071     2322975    72520256      0      0  0
2529589 /usr/src/sys/netinet/ip_input.c:1315 (sleep mutex:rtentry)
       3        17     3665247     3715117    72520256      0      0  0
8425384 /usr/src/sys/netinet/in_rmx.c:114 (sleep mutex:rtentry)


On Sun, Jul 27, 2014 at 1:50 PM, Adrian Chadd <adrian@freebsd.org> wrote:

> Yeah, there's something odd going on. You shouldn't see any of that
> lock contention if flowtable is enabled. Thus I think there's
>
> Oh wait, the fastfwd code doesn't know about flowtables. I just looked
> at it (sys/netinet/ip_fastfwd.c.)
>
> Try disabling fastfwd for a test and see if the lock profile improves.
> (Set debug.lock.prof.reset=1 to clear the profiling data before you do it.)
>
>
> -a
>
>
> On 27 July 2014 05:58, John Jasen <jjasen@gmail.com> wrote:
> > I shouldn't even be coming close to maxflows in this test scenario.
> >
> > net.flowtable.enable: 1
> > net.flowtable.maxflows: 1042468
> >
> > On 07/26/2014 10:20 PM, Adrian Chadd wrote:
> >> Flowtable is enabled? That's odd, it shouldn't be showing up like that.
> >>
> >>
> >>
> >> -a
> >>
> >>
> >>
> >
>



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