From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: HVM performance once again
Date: Wed, 31 May 2023 10:24:44 +0200 [thread overview]
Message-ID: <ZHcETJZThCdr22MW@Air-de-Roger> (raw)
In-Reply-To: <ZHb8DBbRuklAXhCE@mail-itl>
On Wed, May 31, 2023 at 09:49:32AM +0200, Marek Marczykowski-Górecki wrote:
> Hi,
>
> I returned to HVM performance once again, this time looking at PCI
> passthrough impact evaluating network throughput.
> The setup:
> - Xen 4.17
> - Linux 6.3.2 in all domU
> - iperf -c running in a PVH (call it "client")
> - iperf -s running in a HVM (call it "server")
> - client's netfront has a backend directly in server
> - frontend's "trusted" is set to 0
> - HVM have qemu in a stubdomain in all the cases
> - no intentional differences about HVM besides presence of a PCI device
> (it is a network card, but it was not involved in the traffic)
>
> And now the results:
> - server is plain HVM: ~6Gbps
> - server is HVM and has some PCI passthrough: ~3Gbps
>
> Any idea why such huge difference?
Just a wild guess, when domains have a PCI device assigned the memory
cache types from the guest are enforced, otherwise it all defaults to
write-back (see epte_get_entry_emt()).
If you are not using the PCI device you might want to play with
epte_get_entry_emt() and see if that makes a difference.
Do you see the same performance regression when testing on AMD?
Thanks, Roger.
prev parent reply other threads:[~2023-05-31 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 7:49 HVM performance once again Marek Marczykowski-Górecki
2023-05-31 8:24 ` Roger Pau Monné [this message]
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=ZHcETJZThCdr22MW@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=marmarek@invisiblethingslab.com \
--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.