Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Apr 2021 13:19:23 +0000
From:      Rick Macklem <rmacklem@uoguelph.ca>
To:        Kevin Bowling <kevin.bowling@kev009.com>
Cc:        FreeBSD Net <freebsd-net@freebsd.org>
Subject:   Re: Client Networking Issues / NIC Lab
Message-ID:  <YQXPR0101MB0968C64183DEDEF76AD3EE77DD459@YQXPR0101MB0968.CANPRD01.PROD.OUTLOOK.COM>
In-Reply-To: <CACNAnaEah_4JT=NHWPUJu8CdrD83CJbmVvjNJse0WVmW4Wz6nw@mail.gmail.com>
References:  <CAK7dMtBy=wvi4=ES6yhO0t%2BVfXcjcTtSuMK1_Vt3t3eZPY53Yg@mail.gmail.com>, <CACNAnaEah_4JT=NHWPUJu8CdrD83CJbmVvjNJse0WVmW4Wz6nw@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Kyle Evans wrote:=0A=
>On Fri, Apr 23, 2021 at 12:22 AM Kevin Bowling <kevin.bowling@kev009.com> =
wrote:=0A=
>>=0A=
>> Greetings,=0A=
>>=0A=
>> [... snip ...]=0A=
>>=0A=
>> Tehuti Networks seems to have gone out of business.  Probably not=0A=
>> worth worrying about.=0A=
>>=0A=
>=0A=
>That's unfortunate. I had a box of their 10G NICs and I got them to=0A=
>put a driver up for review[0][1], but they weren't very responsive and=0A=
>the existing codebase was in pretty rough shape.=0A=
>=0A=
>Beyond that, your #3 seems to be the most appealing. #2 could probably=0A=
>work in the mid-to-long term, but we'd likely be better off=0A=
>bootstrapping interest with solid community-supported drivers then=0A=
>reaching out to vendors once we can demonstrate that plan field of=0A=
>dreams can work and drive some substantial amount of business.=0A=
=0A=
I'll admit to knowing nothing about it, but is using the linuxKPI=0A=
to port Linux drivers into FreeBSD feasible?=0A=
=0A=
Obviously, given the size of the Linux community, it seems=0A=
more likely that it will have a driver that handles many chip=0A=
variants, plus updates for newer chips, I think.=0A=
=0A=
I do agree that having drivers that at least work for the=0A=
basics (maybe no Netmap, TSO, or similar) for the=0A=
commodity chips would make it easier for new adopters=0A=
of FreeBSD. (I avoid the problem by finding old, used=0A=
hardware. The variants of Intel PRO1000 and re chips I=0A=
have work fine with the drivers in FreeBSD13/14.;-)=0A=
=0A=
Oh, and if TSO support is questionable, I think it would be=0A=
better to leave it disabled and at least generate a warning=0A=
when someone enables it, if it can be enabled at all.=0A=
=0A=
Good luck with it, rick=0A=
=0A=
Thanks,=0A=
=0A=
Kyle Evans=0A=
=0A=
[0] https://reviews.freebsd.org/D18856=0A=
[1] https://reviews.freebsd.org/D19433=0A=
_______________________________________________=0A=
freebsd-net@freebsd.org mailing list=0A=
https://lists.freebsd.org/mailman/listinfo/freebsd-net=0A=
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"=0A=
=0A=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?YQXPR0101MB0968C64183DEDEF76AD3EE77DD459>