[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Possible bug? DOM-U network stopped working after fatal error reported in DOM0
- To: Paul Leiber <paul@xxxxxxxxxxxxxxxx>, "G.R." <firemeteor@xxxxxxxxxxxxxxxxxxxxx>
- From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Date: Thu, 3 Nov 2022 13:22:07 +0100
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=3t9xB6iOPr8y/byF6KKMPelveYpY7HLpyDfj/bV7PVo=; b=Q/vIyR3b9cdldzARxh9zgKntnVNYIrKaZYKPnwDEX+WkPtAM+wy7a8XpNJZpKKQrPCwazrGNXf70PGHEw1Gbx61R8N4FAwLlr88Wsl5w/8lqtKuN2bfwooMHl9jL3X26H0AWQa9acz4qvWP2EPST8QtQbkrcsXC2iCF7aZlQQVyG/LGNZ3wlLOTAnCoa+c6Abw4qezeW0DhOR1h8aVMzgbZ53s9l226NyYtAoAmdVXp6le3LafBCVeiUcRZI4u30PNX10kQsOcR3f4kQXVRC28KBSJcBKkvKGIUCC+Jwrpbg6teui30spWSQ3qvISrPAwpeTilvc5xvURuEivwP6eA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=F6iv+zR8Oy3nVRaPzJ9Qi5EsHKXa3DdCwmsxUBCtG7Bqb2g+ZcKbscpxqwnODVi1sUplr6Q6ILkj5oC7PQdbrmWAt8qKx6C60R112Ylm54JRSt0O0LwDvVrjkXvJeTvAwsv9ztqbDwDwjzWz46cPnHAmUzzmlTGRG8fpgk427qcr284N3AkzUPg2AaQoDjkuhUntOCe6R3fHuYDmvBBKU/YlW8NCDirhR4X+yAAnzZO4mWF3tw1MlQGwrYooqZ60hj4AgfavWGHy5SUtBStGLVvpd3cSovlVUET6AMjcIEfxnxMjXaE08BvBfOwL44oNae4jJJgNLfGo4ccBD/8qBw==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx
- Delivery-date: Thu, 03 Nov 2022 12:22:32 +0000
- Ironport-data: A9a23:UeNm7KM7CIxZayTvrR2blsFynXyQoLVcMsEvi/4bfWQNrUongjQFy GUZWm7TaK6LN2akKIp3OY6w8U9Svp/cyddkHgto+SlhQUwRpJueD7x1DKtS0wC6dZSfER09v 63yTvGacajYm1eF/k/F3oDJ9CU6jufQA+KmU4YoAwgpLSd8UiAtlBl/rOAwh49skLCRDhiE/ Nj/uKUzAnf8s9JPGj9Suv/rRC9H5qyo4mpB5gdmPJingXeF/5UrJMNHTU2OByOQrrl8RoaSW +vFxbelyWLVlz9F5gSNy+uTnuUiG9Y+DCDW4pZkc/HKbitq/0Te5p0TJvsEAXq7vh3S9zxHJ HehgrTrIeshFvWkdO3wyHC0GQkmVUFN0OevzXRSLaV/ZqAJGpfh66wGMa04AWEX0spYGGJg7 6YWFBMURTWZ2MeZ8ainY+Y506zPLOGzVG8ekldJ6GmDSNoDGtXESaiM4sJE1jAtgMwIBezZe 8cSdTtoalLHfgFLPVAUTpk5mY9EhFGmK2Ee9A3T+PRxvzS7IA9ZidABNPLPfdOHX4NNl1uwr WPa5WXpRBodMbRzzBLVrCz23bWQxksXXqoyV+GC+6A7p2bD22k0JhYIXACWk8uQ3xvWt9V3b hZ8FjAVhbA76UiDSd/5Xhu1u3WEoxQYUpxcHoUS5gCXx6/Z/wueHEAZVTNbc5o9s9IsTjEk0 UWGkpXvCCAHmK2YTzeR+6mZqRu2ODMJNikSaCkcVwwH7tL/5oYpgXryos1LFae0ipj5HGr2y jXS9iwm3e1P0YgMyrmx+k3Bj3S0vJ/VQwUp5wLRGGW48gd+Y43jbIutgbTG0ct9wE+iZgHpl BA5dwK2tYji0bnlePSxfdgw
- Ironport-hdrordr: A9a23:YyjKDa0uw5dixSNsQ5lhzAqjBEgkLtp133Aq2lEZdPU0SKGlfg 6V/MjztCWE7Ar5PUtLpTnuAsa9qB/nm6KdgrNhWItKPjOW21dARbsKheffKlXbcBEWndQtt5 uIHZIeNDXxZ2IK8PoT4mODYqodKA/sytHWuQ/cpU0dMz2Dc8tbnmBE4p7wKDwMeOFBb6BJcq a01458iBeLX28YVci/DmltZZm4mzWa/KiWGCLvHnQcmXGzsQ8=
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On Thu, Nov 03, 2022 at 07:58:52AM +0100, Paul Leiber wrote:
>
>
> Am 30.10.2022 um 17:36 schrieb G.R.:
> > On Mon, Jan 10, 2022 at 10:54 PM Roger Pau Monné <roger.pau@xxxxxxxxxx>
> > 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.
Hello to both,
Sorry, I completely dropped the ball on that patch, didn't even
remember I had it pending :(.
Will do a build test with it and commit later today, I don't think I
will get any feedback, and it seems to improve the situation for your
use-cases.
Thanks, Roger.
|
