Current state of Intel XL710 40G NIC ixl performance

I am having trouble getting an Intel XL710-DA2 NIC to get even close to line rate. It is a 4x10 Gbps card. The box is running FreeBSD 11 (FreeNAS in particular). We have tried both 1.7 and 1.9 driver revisions with similar results. The NVM version is 5.05. The card is in a confirmed 8x slot

Re: removal of token-ring infrastructure coming soon

> > On Mar 27, 2018, at 5:56 PM, Rodney W. Grimes > > wrote: > > > >> I have posted a revision which removes support for token-ring networking > >> from the tree. There have been no such devices for some time. > >> > >> https://reviews.freebsd.org/D14875 >

Re: removal of token-ring infrastructure coming soon

> On Mar 27, 2018, at 5:56 PM, Rodney W. Grimes > wrote: > >> I have posted a revision which removes support for token-ring networking >> from the tree. There have been no such devices for some time. >> >> https://reviews.freebsd.org/D14875 >> > >

Re: removal of token-ring infrastructure coming soon

> I have posted a revision which removes support for token-ring networking > from the tree. There have been no such devices for some time. > > https://reviews.freebsd.org/D14875 > Arcnet coming soon? and probably FDDI? -- Rod Grimes

removal of token-ring infrastructure coming soon

I have posted a revision which removes support for token-ring networking from the tree. There have been no such devices for some time. https://reviews.freebsd.org/D14875 -- Brooks signature.asc Description: PGP signature

Re: Same host or different? How can you tell "over the wire"?

"Ronald F. Guilmette" wrote: > In message <201803241747.w2ohlupr069...@donotpassgo.dyslexicfish.net>, > Jamie Landeg-Jones wrote: > > >Have you thought of examining the TCP timestamp field? Not necessarily > >for accurate uptime, but a way to

Re: [vnet] [epair] epair interface stops working after some time

Excellent, will give it a try on a box that I never have this problem on. Will let you know of the symptoms are the same when I trigger it. Best, Reshad On 28 March 2018 12:32:44 AM IST, Kristof Provost wrote: >On 27 Mar 2018, at 20:59, Reshad Patuck wrote: >> The current

Re: [vnet] [epair] epair interface stops working after some time

On 27 Mar 2018, at 20:59, Reshad Patuck wrote: The current value of 'net.link.epair.netisr_maxqlen' is 2100, I will make it 210. Will this require a reboot? or can I just change the sysctl and reload the epair module? ​ You shouldn’t need to reboot or reload the epair module. When I set it to

Re: [vnet] [epair] epair interface stops working after some time

Hi, ​ @Kristof: The current value of 'net.link.epair.netisr_maxqlen' is 2100, I will make it 210. Will this require a reboot? or can I just change the sysctl and reload the epair module? ​ @Bjoern: here is the output to 'netstat -Q' ``` # netstat -Q Configuration: Setting

Re: [vnet] [epair] epair interface stops working after some time

On 27 Mar 2018, at 16:48, Bjoern A. Zeeb wrote: On 27 Mar 2018, at 14:40, Kristof Provost wrote: (Re-cc freebsd-net, because this is useful information) On 27 Mar 2018, at 13:07, Reshad Patuck wrote: The epair crash occurred again today running the epair module code with the added dtrace

Re: netmap ixgbevf mtu

Grazie mille. I will test it as time allows -- swamped. Joe Buehler Vincenzo Maffione wrote: > Hi, > This commit (fe13476b106ed1f4b517b1590e1dfb3f268b6e78) in the upstream > netmap should have fixed the NS_MOREFRAG issue for ixgbe. > If you happen give a try let us know. > > Cheers, >

[Bug 191700] [carp] [bridge] CARP does not work on interface which belongs to a bridge

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191700 Hauke Fath changed: What|Removed |Added CC|

Re: [vnet] [epair] epair interface stops working after some time

On 27 Mar 2018, at 14:40, Kristof Provost wrote: (Re-cc freebsd-net, because this is useful information) On 27 Mar 2018, at 13:07, Reshad Patuck wrote: The epair crash occurred again today running the epair module code with the added dtrace sdt providers. ​ Running the same command as last

Re: [vnet] [epair] epair interface stops working after some time

On 27 Mar 2018, at 16:40, Kristof Provost wrote: > It’s probably worth trying to play with ‘net.route.netisr_maxqlen’. I probably mean ‘net.link.epair.netisr_maxqlen’ here. Regards, Kristof ___ freebsd-net@freebsd.org mailing list

Re: [vnet] [epair] epair interface stops working after some time

(Re-cc freebsd-net, because this is useful information) On 27 Mar 2018, at 13:07, Reshad Patuck wrote: The epair crash occurred again today running the epair module code with the added dtrace sdt providers. ​ Running the same command as last time, 'dtrace -n ::epair\*:' returns the following:

Re: netmap ixgbevf mtu

Hi, This commit (fe13476b106ed1f4b517b1590e1dfb3f268b6e78) in the upstream netmap should have fixed the NS_MOREFRAG issue for ixgbe. If you happen give a try let us know. Cheers, Vincenzo 2018-03-21 21:40 GMT+01:00 Vincenzo Maffione : > I see. Unfortunately this breaks