Date: Tue, 9 Apr 2019 14:19:18 -0400 From: Nick Rogers <ncrogers@gmail.com> To: Graham Menhennitt <graham@menhennitt.com.au> Cc: FreeBSD STABLE <freebsd-stable@freebsd.org> Subject: Re: em performs worse than igb (latency wise) in 12? Message-ID: <CAKOb=YaFV88vzmPsH0TjSuBefbUts8VSjRumuX98RRtZDvh0wQ@mail.gmail.com> In-Reply-To: <81e63eaf-352d-4b29-a4c0-9085e699931e@menhennitt.com.au> References: <b910baa6-6428-67fa-5df4-49b777e770d1@swishmail.com> <7673edad-1e50-7e9b-961e-f28ab7a0f41e@ingresso.co.uk> <ce9e5132-534f-1c24-7245-51cd61d660fc@swishmail.com> <81e63eaf-352d-4b29-a4c0-9085e699931e@menhennitt.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Apr 6, 2019 at 10:24 PM Graham Menhennitt <graham@menhennitt.com.au> wrote: > Not that it's at all relevant to the question here, but... > > It does mostly work without em in the 12 kernel - I'm not sure how, but > it does. > > I upgraded to 12-stable via source but didn't add em to my custom > kernel. Most things worked - basic network functionality. But I had > problems with ipfw and igb. Adding em to the kernel fixed them. > FWIW the latest GENERIC kernel includes the iflib, em, etc devices as far as I can tell. I found the new UPDATING entry about iflib "no longer unconditionally compiled into the kernel" a bit confusing... So long as you are including GENERIC it should be the same as 12-RELEASE. > Graham > > On 6/4/19 6:12 am, Kris von Mach wrote: > > On 4/6/2019 2:56 AM, Pete French wrote: > >> Something odd going on there there - I am using 12-STABLE and I have > >> igb just fine, and it attaches to the same hardware that 11 did: > > > > It does work in 12, throughput is great, just that the latency is > > higher than 11. > > > > igb0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu > > 1500 > > > options=e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6> > > > > > ether 38:ea:a7:8d:c1:6c > > inet 208.72.56.19 netmask 0xfffffc00 broadcast 208.72.59.255 > > inet6 fe80::3aea:a7ff:fe8d:c16c%igb0 prefixlen 64 scopeid 0x1 > > inet6 2602:ffb8::208:72:56:9 prefixlen 64 > > media: Ethernet autoselect (1000baseT <full-duplex>) > > status: active > > nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL> > > > >> Do you have a custom kernel, and if so did you see this note in > >> UPDATING? > > > > Yes I do, but it includes all of GENERIC which includes em drivers, > > otherwise it wouldn't even work with the network card. > > > > my custom kernel: > > > > include GENERIC > > ident CUSTOM > > makeoptions WITH_EXTRA_TCP_STACKS=1 > > options TCPHPTS > > options SC_KERNEL_CONS_ATTR=(FG_GREEN|BG_BLACK) > > options IPSTEALTH > > options AHC_REG_PRETTY_PRINT # Print register bitfields in debug > > options AHD_REG_PRETTY_PRINT # Print register bitfields in debug > > device cryptodev > > device aesni > > > > I did try without RACK just in case that was the culprit. > > > > > > _______________________________________________ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org > " > _______________________________________________ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKOb=YaFV88vzmPsH0TjSuBefbUts8VSjRumuX98RRtZDvh0wQ>