xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Samuel Verschelde <samuel.verschelde@vates.fr>
Cc: <xen-devel@lists.xenproject.org>
Subject: Re: XSA-332 kernel patch - huge network performance on pfSense VMs
Date: Mon, 18 Jan 2021 11:03:40 +0100	[thread overview]
Message-ID: <20210118100340.6vryyk52f5pyxgwv@Air-de-Roger> (raw)
In-Reply-To: <dc5d60d7-1ada-5eb1-ff91-495d663ca89e@vates.fr>

On Fri, Jan 15, 2021 at 03:03:26PM +0000, Samuel Verschelde wrote:
> Hi list,
> 
> Another "popular" thread on XCP-ng forum [1], started in october 2020,
> allowed us to detect that patch 12 from the XSA-332 advisory [2] had a very
> significant impact on network performance in the case of pfSense VMs.
> 
> We reproduced the issue internally (well, we reproduced "something". The
> user setups in this thread are diverse) and our findings seem to confirm
> what the users reported. Running iperf3 from the pfSense VM to a debian VM
> gives results around 5 times slower than before. Reverting this single patch
> brings the performance back. On the debian to pfSense direction, the drop is
> about 25%.

pfSense is based on FreeBSD, so I would bet that whatever performance
degradation you are seeing would also happen with plain FreeBSD. I
would assume netfront in FreeBSD is triggering the ratelimit on Linux,
and hence it gets throttled.

Do you think you have the bandwidth to look into the FreeBSD side and
try to provide a fix? I'm happy to review and commit in upstream
FreeBSD, but would be nice to have someone else also in the loop as
ATM I'm the only one doing FreeBSD/Xen development AFAIK.

Thanks, Roger.


  reply	other threads:[~2021-01-18 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15 15:03 XSA-332 kernel patch - huge network performance on pfSense VMs Samuel Verschelde
2021-01-18 10:03 ` Roger Pau Monné [this message]
2021-01-26 14:46   ` Samuel Verschelde
2021-01-26 15:04   ` Samuel Verschelde
2021-02-03 20:47     ` Andrew Cooper

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=20210118100340.6vryyk52f5pyxgwv@Air-de-Roger \
    --to=roger.pau@citrix.com \
    --cc=samuel.verschelde@vates.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).