From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 2BCF9C433FE for ; Thu, 3 Nov 2022 06:59:30 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.436125.690197 (Exim 4.92) (envelope-from ) id 1oqUBl-00057l-Ss; Thu, 03 Nov 2022 06:58:57 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 436125.690197; Thu, 03 Nov 2022 06:58:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1oqUBl-00057e-QL; Thu, 03 Nov 2022 06:58:57 +0000 Received: by outflank-mailman (input) for mailman id 436125; Thu, 03 Nov 2022 06:58:57 +0000 Received: from se1-gles-flk1-in.inumbo.com ([94.247.172.50] helo=se1-gles-flk1.inumbo.com) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1oqUBk-00057Y-U7 for xen-devel@lists.xenproject.org; Thu, 03 Nov 2022 06:58:57 +0000 Received: from mo4-p00-ob.smtp.rzone.de (mo4-p00-ob.smtp.rzone.de [85.215.255.20]) by se1-gles-flk1.inumbo.com (Halon) with ESMTPS id fac11bef-5b44-11ed-8fd0-01056ac49cbb; Thu, 03 Nov 2022 07:58:54 +0100 (CET) Received: from mail.onlineschubla.de by smtp.strato.de (RZmta 48.2.1 DYNA|AUTH) with ESMTPSA id U559b8yA36wrPKP (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate) for ; Thu, 3 Nov 2022 07:58:53 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.onlineschubla.de (Postfix) with ESMTP id 3DDDB201C6 for ; Thu, 3 Nov 2022 07:58:53 +0100 (CET) Received: from mail.onlineschubla.de ([127.0.0.1]) by localhost (mail.onlineschubla.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iZOmTMO2LQqH for ; Thu, 3 Nov 2022 07:58:52 +0100 (CET) Received: from [192.168.178.167] (unknown [192.168.12.2]) by mail.onlineschubla.de (Postfix) with ESMTPA id 4766520157 for ; Thu, 3 Nov 2022 07:58:52 +0100 (CET) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: fac11bef-5b44-11ed-8fd0-01056ac49cbb DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1667458733; s=strato-dkim-0002; d=onlineschubla.de; h=In-Reply-To:From:References:To:Subject:Date:Message-ID:Cc:Date:From: Subject:Sender; bh=HL5Rs1p4VGc86jYsZXj8jtLsWSZG7/oFL/FWfFH+RzY=; b=KnCgqQSP96edQgD3epReU4cvuNr7zev1c97DU2L/CMt524hloWr6z1wZLD0NJACDoT x0uDdzmjD0Nnx5fzQdnRkGwraNc7pxKTolTZA+1waa7R3dvDIFNLIkiQN6r8IzgCqJ4d jNiW9EHPYqO/eAD1gjqlsin2A1mhWoG+YEAxS9+RFG9j2pKKg3PTsWmlJJcI0ULu7OwC OiDsEG43tt7wmBRBOKACGk9OHD9CSLk3b9BRgaOrUen9/ZQZXEUGuN3orUPXyxksY61r 1SjtCpW1MUDZx0A8dlmqJmk7dP+tu3rLEHKjCVk1WO8wOVau5YEiPO9tWYPJA+DZRmEt +6Dg== Authentication-Results: strato.com; dkim=none X-RZG-AUTH: ":PG0ReWCndfO3rCSML4AvNaDxJ7WJyilEI/NMX3IPsStZLbcZC9mNZx0oO96cCwabxEcCkdg/gSnE" X-RZG-CLASS-ID: mo00 X-Virus-Scanned: Debian amavisd-new at onlineschubla.de Message-ID: <735adbe4-238b-bb7b-ba91-eb53759223aa@onlineschubla.de> Date: Thu, 3 Nov 2022 07:58:52 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.4.1 Subject: Re: Possible bug? DOM-U network stopped working after fatal error reported in DOM0 Content-Language: en-US To: xen-devel@lists.xenproject.org References: From: Paul Leiber In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Am 30.10.2022 um 17:36 schrieb G.R.: > On Mon, Jan 10, 2022 at 10:54 PM Roger Pau Monné wrote: >>> So looks like at least the imbalance between two directions are not >>> related to your patch. >>> Likely the debug build is a bigger contributor to the perf difference >>> in both directions. >>> >>> I also tried your patch on a release build, and didn't observe any >>> major difference in iperf3 numbers. >>> Roughly match the 30Gbps and 1.xGbps number on the stock release kernel. >> Thanks a lot, will try to get this upstream then. >> >> Roger. > Hi Roger, any news for the upstream fix? I haven't heard any news since... > The reason I came back to this thread is that I totally forgot about > this issue and upgraded to FreeNAS 13 only to rediscover this issue > once again :-( > > Any chance the patch can apply on FreeBSD 13.1-RELEASE-p1 kernel? > > Thanks, > G.R. > Hi, I want to confirm that the patch in an official release would make quite some people very happy. E.g. among OPNsense users, there are some who suffer from the network issue [1]. FWIW, I compiled a kernel including Roger's patch, and it seems to be working without trouble in my OPNsense DomU. Best regards, Paul [1] https://forum.opnsense.org/index.php?topic=28708.15