Date: Wed, 19 Aug 2020 17:28:29 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 230465] ixl: not working in netmap mode Message-ID: <bug-230465-7501-yNmxa9L3F9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230465-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-230465-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230465 --- Comment #39 from Vincenzo Maffione <vmaffione@FreeBSD.org> --- (In reply to Kubilay Kocak from comment #38) This is not a suricata issue. There was a suricata issue mentioned in this thread, but it has been fixed upstream (suricata). Comment #37 seems unrelated, since it mentions netmap with ixl in 12.x, whe= re iflib is in use. There was an iflib/netmap bug (see https://reviews.freebsd.org/D25252) that may explain the problems briefly mentioned in #37. But that is now in HEAD and stable/12. This report is about a bug that apparently affects netmap TX over ixl in 11= .x (but not in 12.x and ahead). This change https://reviews.freebsd.org/D18984 does some cleanup but it does not fix the bug. As you can see in the discussion, I reported the issue to the Intel develop= ers, but as far as I know there have been no changes on their side (in stable/11= ). So I can assume that the bug is still there, and it's something that need t= he Intel developers attention, if someone is still interested in netmap+ixl in 11.x --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230465-7501-yNmxa9L3F9>