From owner-freebsd-net@freebsd.org Wed Nov 22 09:19:02 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28AA9DE5CDB for ; Wed, 22 Nov 2017 09:19:02 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B854373618 for ; Wed, 22 Nov 2017 09:19:01 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (mh0.gentlemail.de [78.138.80.135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id vAM9Ix7n084990; Wed, 22 Nov 2017 10:18:59 +0100 (CET) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (s1.omnilan.de [217.91.127.234]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id 077F9AA9; Wed, 22 Nov 2017 10:18:58 +0100 (CET) Message-ID: <5A154102.10007@omnilan.de> Date: Wed, 22 Nov 2017 10:18:58 +0100 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Vincenzo Maffione CC: "freebsd-net@freebsd.org" , Giuseppe Lettieri Subject: Re: netmap/vale periodic deadlock References: <5A0F14CD.3040407@omnilan.de> <5A149107.9060507@omnilan.de> <5A1537B3.9030603@omnilan.de> In-Reply-To: <5A1537B3.9030603@omnilan.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Greylist: ACL 129 matched, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [78.138.80.130]); Wed, 22 Nov 2017 10:18:59 +0100 (CET) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: 78.138.80.135; Sender-helo: mh0.gentlemail.de; ) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Nov 2017 09:19:02 -0000 Bezüglich Harry Schmalzbauer's Nachricht vom 22.11.2017 09:39 (localtime): > Bezüglich Vincenzo Maffione's Nachricht vom 22.11.2017 09:04 (localtime): >> >> 2017-11-21 21:48 GMT+01:00 Harry Schmalzbauer > >: >> >> Bezüglich Vincenzo Maffione's Nachricht vom 21.11.2017 09:39 >> (localtime): >> … >> > >> > If this is the case, although you are allowed to do that, I don't think >> > it's a convenient way to use netmap. >> > Since VLAN interfaces like vlan0 do not have (and cannot have) native >> > netmap support, you are falling back to emulated netmap adapters (which >> > are probably buggy on FreeBSD, specially when combined with VALE). >> > Apart from bugs I think that with this setup you can't get decent >> > performance that would justify using netmap rather than the standard >> > kernel bridge and TAP devices. >> >> Hello, >> >> lockup happened earlier than expected. >> This time 'vale-ctl' still reported (-l) the configuration. >> One guest, using if_vtnet(4)-virtio-net#vale2:korso, showed: >> dmz: watchdog timeout on queue 0 >> (dmz is the renamed if_vtnet(4)) >> >> I could attach tcpdump to the uplink interface and also to all vlan >> children. >> Complete silence everywhere. So it seems the nic stopped processing >> anything. >> >> Do you think that symptom could be caused by my special vale >> integration, so that bugs in netmap emulation could crash the NIC? >> Or is it unlikely that this is related. >> >> I hadn't prepared a debug kernel for the host, so the machine rebooted >> without again. >> I think I'll have to start with replacing vale first, to narrow down >> possible causes. Today I was lucky, the lockup happend after business >> hours, but I won't rely on that. >> At least I know if I really need to look for a debug netmap kernel, or >> possibly there's something else... >> >> Thanks, >> >> -harry >> >> >> >> I can't really say anything without a stack trace or meaningful logs. >> There is a thing that you may do to see if the bug comes out of a bad >> interaction between >> emulated netmap and VALE. >> Instead of attaching the vlan interfaces to VALE you can connect VALE to >> the vlan interface >> through the "bridge" program. In this way nothing changes from the >> functional point of view, >> but you are not attaching anymore the VLAN interface to VALE (and you >> are using an additional process). >> >> So instead of >> >> # vale-ctl vale0:vlan0 >> >> you would have >> >> # bridge netmap:vlan0 vale0:vv # "vv" can be anything > Hello Vincenzo, > > thank you very much for that interesting hint. > I prepared a netgraph setup yesterday evening, but I'll try your > suggestion first. Unfortunately I don't have time to prepare a debug Since this doesn't need a reboot and I'm in adventure mood, I just tried it at runtime. Unfortunately I can't find bridge documentation besides the source code. It doesn't detach from terminal here: bridge built Oct 8 2017 12:59:57 060.359974 main [244] ------- zerocopy NOT supported 060.359987 main [251] Wait 4 secs for link to come up... 064.365872 main [255] Ready to go, nic1_egn 0x0/1 <-> vale4:nic1egn 0x0/1. 068.084364 main [306] poll timeout [0] ev 1 0 rx 0@33 tx 1022, [1] ev 1 0 rx 0@34 tx 1023 072.565559 main [306] poll timeout [0] ev 1 0 rx 0@34 tx 1022, [1] ev 1 0 rx 0@35 tx 1023 … In general, things are working. Is bridge staing in the foreground by design? Thanks, -harry