From owner-freebsd-net@freebsd.org Tue Sep 4 14:44:17 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C69F4FF16E1 for ; Tue, 4 Sep 2018 14:44:17 +0000 (UTC) (envelope-from zec@fer.hr) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6BD6D726BD for ; Tue, 4 Sep 2018 14:44:17 +0000 (UTC) (envelope-from zec@fer.hr) Received: by mailman.ysv.freebsd.org (Postfix) id 2C8A8FF16DF; Tue, 4 Sep 2018 14:44:17 +0000 (UTC) Delivered-To: net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1B42AFF16DD for ; Tue, 4 Sep 2018 14:44:17 +0000 (UTC) (envelope-from zec@fer.hr) Received: from mail.fer.hr (mail.fer.hr [161.53.72.233]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.fer.hr", Issuer "TERENA SSL CA 3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 99148726BC for ; Tue, 4 Sep 2018 14:44:16 +0000 (UTC) (envelope-from zec@fer.hr) Received: from x23 (31.147.123.108) by MAIL.fer.hr (161.53.72.233) with Microsoft SMTP Server (TLS) id 14.3.399.0; Tue, 4 Sep 2018 16:43:04 +0200 Date: Tue, 4 Sep 2018 16:43:03 +0200 From: Marko Zec To: John-Mark Gurney CC: Vincenzo Maffione , Luigi Rizzo , "freebsd-net@freebsd.org" Subject: Re: vale and netmap module questions Message-ID: <20180904164303.68c43b6e@x23> In-Reply-To: <20180901211123.GZ45503@funkthat.com> References: <20180901014953.GV45503@funkthat.com> <20180901211123.GZ45503@funkthat.com> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Originating-IP: [31.147.123.108] X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Sep 2018 14:44:17 -0000 On Sat, 1 Sep 2018 14:11:23 -0700 John-Mark Gurney wrote: > Vincenzo Maffione wrote this message on Sat, Sep 01, 2018 at 22:25 > +0200: ... > > On x86_64 netmap is not built as a module, so everything works > > fine. I don't see any reason why it should be a module in aarch64. > > Well, sys/modules/netmap exists... If it isn't planned on ever being > made to work, it should be removed so people don't get confused, or > at least marked broken so it doesn't get built... > > I built it manually because it was quicker than recompiling an entire > kernel and rebooting... Hi John-Mark, out of curiosity I tested all four kernel config combinations with "device netmap" and "options VIMAGE" being on and off (both are on by default now in GENERIC) on amd64 @r338446, and found that kldloading netmap.ko can't provoke a panic. Was there a particular sequence of commands issued after kldloading netmap which led to the crash you reported earlier? Nevertheless, note that building the kernel without "device netmap" is borderline pointless even if netmap core built as a kld module works, as this will result in all the drivers being built without the required netmap bits, which means they will only work in the painfully slow "emulation" mode with netmap. Perhaps the panic you stepped into was related to the emulation mode being used with netmap, instead of using the native netmap hooks in device drivers? Or maybe was it vale + VNET related? Marko