Client Networking Issues / NIC Lab

[Rick Macklem]

Kyle Evans wrote:
>On Fri, Apr 23, 2021 at 12:22 AM Kevin Bowling <kevin.bowling at kev009.com> wrote:
>>
>> Greetings,
>>
>> [... snip ...]
>>
>> Tehuti Networks seems to have gone out of business.  Probably not
>> worth worrying about.
>>
>
>That's unfortunate. I had a box of their 10G NICs and I got them to
>put a driver up for review[0][1], but they weren't very responsive and
>the existing codebase was in pretty rough shape.
>
>Beyond that, your #3 seems to be the most appealing. #2 could probably
>work in the mid-to-long term, but we'd likely be better off
>bootstrapping interest with solid community-supported drivers then
>reaching out to vendors once we can demonstrate that plan field of
>dreams can work and drive some substantial amount of business.

I'll admit to knowing nothing about it, but is using the linuxKPI
to port Linux drivers into FreeBSD feasible?

Obviously, given the size of the Linux community, it seems
more likely that it will have a driver that handles many chip
variants, plus updates for newer chips, I think.

I do agree that having drivers that at least work for the
basics (maybe no Netmap, TSO, or similar) for the
commodity chips would make it easier for new adopters
of FreeBSD. (I avoid the problem by finding old, used
hardware. The variants of Intel PRO1000 and re chips I
have work fine with the drivers in FreeBSD13/14.;-)

Oh, and if TSO support is questionable, I think it would be
better to leave it disabled and at least generate a warning
when someone enables it, if it can be enabled at all.

Good luck with it, rick

Thanks,

Kyle Evans

[0] https://reviews.freebsd.org/D18856
[1] https://reviews.freebsd.org/D19433
_______________________________________________
freebsd-net at freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe at freebsd.org"