From owner-freebsd-net@freebsd.org Wed Nov 22 08:04:55 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 3B411DE4137 for ; Wed, 22 Nov 2017 08:04:55 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E78C4715EE for ; Wed, 22 Nov 2017 08:04:54 +0000 (UTC) (envelope-from v.maffione@gmail.com) Received: by mail-qk0-x231.google.com with SMTP id a142so15628098qkb.5 for ; Wed, 22 Nov 2017 00:04:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=56wjqg+iV9YX75E6CdeUPuEQ4hTgREksKE28bUdEh+M=; b=lBbhcuOVHYUmXVXu3SDmQqiHnmAM88CB2d+n/qMFd4XMzOqFCvMMxR7PZ9zNxP4Czn pUouPOSxFSrpm4Js9Qir+vvyk10bBrgEuri6Wlncke5v73E8azEyW/Uwh+yYrcNe9uUz 3IPAJUmSGXVwnUMwxmtHcA1faa76gYuxilq/xgIfPsuLqiaCJSl8GrDqvxHbrLP9diD4 tZ/F4agjdOMNKhKQ0qIkzn76CpCUJZdI2TitWrcArafMfgEbw0SpvYhQHipwZfaZmG6H vOM8dDVt3qFEnzQAymNB5S12W4IlNBT2FhvlkgIwxYgWrYC2j4HChWw6oORSWCLl3F3l 0PeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=56wjqg+iV9YX75E6CdeUPuEQ4hTgREksKE28bUdEh+M=; b=G03eDZWIQdBIlBN/LK6biHeBZZEwCTGDJt1yLtOk60OjxXCJGuYRgSRZx6zbnLwQxJ cfL0o6znZp9je5lSj+G0tGhxcpWQvIn2QhqLV0TXqpvv143c8W26NwcudIledWPDfDrK w9rB0EuimFWc+47geCK2K3D+nKKwhLWPeDD9QWmwPBs7NbJ+QY36phQdJEnlhmm3Vkew Ixi5/dmRxIgU3zv1P6qh/q7DRwcbARWWyj/63jp8/5tGwu3LC6L381ffwSiGg5MwCcok Zo9femIiGfso0f/gqcLK96aW8ToOBVNj9KJtbc831D5Y3gdmYMTiZXFV/YTLiyMWrBQd qCZw== X-Gm-Message-State: AJaThX5cFe6zv3BznOCIvRIkTkv5yiflxAf+g3hUxmrpWu23wLEyukUy V3SIAjOdbiZRfrxohzFRCTOd2YmWw6FNPLHVeg8= X-Google-Smtp-Source: AGs4zMbSsez/6XscPdZxInuybJM/vnPAJDnFvsvHWQF03pooKSZm9BT1G4ZokmPNczB9Gha6By6XW31Nl7OcSLFJ4r0= X-Received: by 10.55.151.4 with SMTP id z4mr33117505qkd.173.1511337893846; Wed, 22 Nov 2017 00:04:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.174.25 with HTTP; Wed, 22 Nov 2017 00:04:53 -0800 (PST) In-Reply-To: <5A149107.9060507@omnilan.de> References: <5A0F14CD.3040407@omnilan.de> <5A149107.9060507@omnilan.de> From: Vincenzo Maffione Date: Wed, 22 Nov 2017 09:04:53 +0100 Message-ID: Subject: Re: netmap/vale periodic deadlock To: Harry Schmalzbauer Cc: "freebsd-net@freebsd.org" , Giuseppe Lettieri Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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 08:04:55 -0000 2017-11-21 21:48 GMT+01:00 Harry Schmalzbauer : > Bez=C3=BCglich Vincenzo Maffione's Nachricht vom 21.11.2017 09:39 (localt= ime): > =E2=80=A6 > > > > 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 Cheers, Vincenzo --=20 Vincenzo Maffione