From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Paul Leiber <paul@onlineschubla.de>,
"G.R." <firemeteor@users.sourceforge.net>
Cc: xen-devel@lists.xenproject.org
Subject: Re: Possible bug? DOM-U network stopped working after fatal error reported in DOM0
Date: Thu, 3 Nov 2022 13:22:07 +0100 [thread overview]
Message-ID: <Y2OwzjfUnCFf2EDU@Air-de-Roger> (raw)
In-Reply-To: <735adbe4-238b-bb7b-ba91-eb53759223aa@onlineschubla.de>
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@citrix.com> 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.
next prev parent reply other threads:[~2022-11-03 12:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 18:35 Possible bug? DOM-U network stopped working after fatal error reported in DOM0 G.R.
2021-12-19 6:10 ` Juergen Gross
2021-12-19 17:31 ` G.R.
2021-12-20 17:13 ` G.R.
2021-12-21 13:50 ` Roger Pau Monné
2021-12-21 18:19 ` G.R.
2021-12-21 19:12 ` Roger Pau Monné
2021-12-23 15:49 ` G.R.
2021-12-24 11:24 ` Roger Pau Monné
2021-12-25 16:39 ` G.R.
2021-12-25 18:06 ` G.R.
2021-12-27 19:04 ` Roger Pau Monné
[not found] ` <CAKhsbWY5=vENgwgq3NV44KSZQgpOPY=33CMSZo=jweAcRDjBwg@mail.gmail.com>
2021-12-29 8:32 ` Roger Pau Monné
2021-12-29 9:13 ` G.R.
2021-12-29 10:27 ` Roger Pau Monné
2021-12-29 19:07 ` Roger Pau Monné
2021-12-30 15:12 ` G.R.
2021-12-30 18:51 ` Roger Pau Monné
2021-12-31 14:47 ` G.R.
2022-01-04 10:25 ` Roger Pau Monné
2022-01-04 16:05 ` G.R.
2022-01-05 14:33 ` Roger Pau Monné
2022-01-07 17:14 ` G.R.
2022-01-10 14:53 ` Roger Pau Monné
2022-01-11 14:24 ` G.R.
2022-10-30 16:36 ` G.R.
2022-11-03 6:58 ` Paul Leiber
2022-11-03 12:22 ` Roger Pau Monné [this message]
2022-12-14 6:16 ` G.R.
2024-01-09 11:13 ` Niklas Hallqvist
2024-01-09 13:53 ` Roger Pau Monné
2024-01-19 15:51 ` G.R.
2021-12-20 13:51 ` Roger Pau Monné
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y2OwzjfUnCFf2EDU@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=firemeteor@users.sourceforge.net \
--cc=paul@onlineschubla.de \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.