em performs worse than igb (latency wise) in 12?
ncrogers at gmail.com
Tue Apr 9 18:19:31 UTC 2019
On Sat, Apr 6, 2019 at 10:24 PM Graham Menhennitt <graham at menhennitt.com.au>
> 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.
> 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
> > ether 38:ea:a7:8d:c1:6c
> > inet 18.104.22.168 netmask 0xfffffc00 broadcast 22.214.171.124
> > 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 at freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org
> freebsd-stable at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
More information about the freebsd-stable