Date: Sun, 27 Jul 2014 10:50:45 -0700 From: Adrian Chadd <adrian@freebsd.org> To: John Jasen <jjasen@gmail.com> Cc: FreeBSD Net <freebsd-net@freebsd.org> Subject: Re: fastforward/routing: a 3 million packet-per-second system? Message-ID: <CAJ-VmonMYi-7ZCw-PqiuOp5euAdxbyiHXW-ZW96MWQ8%2B-RV8MA@mail.gmail.com> In-Reply-To: <53D4F77B.9020009@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>
next in thread | previous in thread | raw e-mail | index | archive | help
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?CAJ-VmonMYi-7ZCw-PqiuOp5euAdxbyiHXW-ZW96MWQ8%2B-RV8MA>