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 <jja...@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 >> >> >> > _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
