Date: Mon, 20 Mar 2017 10:40:36 +0100 From: Harry Schmalzbauer <freebsd@omnilan.de> To: Vincenzo Maffione <v.maffione@gmail.com> Cc: freebsd-net <freebsd-net@freebsd.org> Subject: Re: [panic] netmap(4) and if_lagg(4) Message-ID: <58CFA394.8070901@omnilan.de> In-Reply-To: <CA%2B_eA9iajZOUFsnWKdodN7zMvst8wn0xViM4xxEx%2B41jw_0B3g@mail.gmail.com> References: <58CBCD7A.8060301@omnilan.de> <CA%2B_eA9iCT7evWUcZMA_ViKfrZnSHp3OpBTS5c4iJ9=ZjO-Pfgw@mail.gmail.com> <58CC23F5.7060507@omnilan.de> <CA%2B_eA9iajZOUFsnWKdodN7zMvst8wn0xViM4xxEx%2B41jw_0B3g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Bezüglich Vincenzo Maffione's Nachricht vom 17.03.2017 22:28 (localtime): > Two things here: > > - We pushed an important fix to stable/11 1-2 months ago, that prevents > panic on emulated netmap mode. Maybe you are still getting that panic > because you are using an older stable/11 image, you should check. > - If you are using "software devices" like if_lagg or even vlan > interfaces, netmap and VALE won't help you a lot, because the drivers > are not patched for netmap (and cannot be) Thank you for your explanation. I'm aware of loosing most advantages, but it gives me the possibility to use different MTUs with one switch/bridge. I'll try to provide more info about the panic this week. Like discussed offlist, the panic happend on a machine with the mentioned fix (latest stable). Perhaps this panic can be fixed, especialy for the vlan children. Otoh., I guess it's NIC (igb) related and em/igb overhaul will hit stable/11 eventually. And afaik, theres no native netmap support anymore :-( So probably resources are better spent on that instead of fixing a panic which doesn't seem to affect anyone else than me. Thanks, -harry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?58CFA394.8070901>