Date: Tue, 07 Mar 2017 16:10:59 +0100 From: Kajetan Staszkiewicz <vegeta@tuxpowered.net> To: Sepherosa Ziehau <sepherosa@gmail.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Why is MSI-X support disabled on bce(4)? Message-ID: <4257854.XfJjHtrk4r@energia> In-Reply-To: <CAMOc5cxWhDC5CMP10C0E=CxhzWvX9p5=BHej3OyLn-PXe9wbiA@mail.gmail.com> References: <1946092.tUUkk3b7I7@energia> <CAMOc5cxWhDC5CMP10C0E=CxhzWvX9p5=BHej3OyLn-PXe9wbiA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Dnia poniedziałek, 6 marca 2017 16:06:03 CET Sepherosa Ziehau pisze: > On Thu, Mar 2, 2017 at 10:02 PM, Kajetan Staszkiewicz > > <vegeta@tuxpowered.net> wrote: > > To whom it might concern: > > > > Well, at least it does concern me. Why is support for multiple interrupts > > and queues not enabled on bce(4)? > > > > Whole block of code is surrounded with #ifdef 0 ... #endif > > > > https://github.com/freebsd/freebsd/blob/master/sys/dev/bce/if_bce.c#L1108 > > It involves much more work than the commented out MSI-X allocation, like > this: > https://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/b42386ee03a4e688c8 > 64ba8d7094064c63d93dce?hp=be5708901d52be5534d5075eec706f5570b6a0f3 That is sad news. Should I assume that porting this driver from DragonflyBSD to FreeBSD would be impossible? -- | pozdrawiam / greetings | powered by Debian, FreeBSD and CentOS | | Kajetan Staszkiewicz | jabber,email: vegeta()tuxpowered net | | Vegeta | www: http://vegeta.tuxpowered.net | `------------------------^---------------------------------------' [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- iF0EABECAB0WIQSOEQZObv2B8mf0JbnjtFCvbXs6FAUCWL7NgwAKCRDjtFCvbXs6 FLCyAKCPuJFkNiAug8zJp0ip+U1CBupR3wCdH5/8pj4+Ht/ZrnfeKUqWGa/26LM= =UtXb -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4257854.XfJjHtrk4r>