From: Elliott Mitchell <ehem+xen@m5p.com>
To: Anthoine Bourgeois <anthoine.bourgeois@vates.tech>
Cc: xen-devel@lists.xenproject.org, "Juergen Gross" <jgross@suse.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Andrei Semenov" <andrei.semenov@vates.tech>
Subject: Re: [PATCH] xen/netfront: Fix TX response spurious interrupts
Date: Fri, 11 Jul 2025 14:22:20 -0700 [thread overview]
Message-ID: <aHGAjJtz66pRBWsM@mattapan.m5p.com> (raw)
In-Reply-To: <aHDAC3mvysH-0vit@mail.vates.tech>
On Fri, Jul 11, 2025 at 07:41:02AM +0000, Anthoine Bourgeois wrote:
> On Thu, Jul 10, 2025 at 01:05:47PM -0700, Elliott Mitchell wrote:
> >On Thu, Jul 10, 2025 at 04:11:15PM +0000, Anthoine Bourgeois wrote:
> >> We found at Vates that there are lot of spurious interrupts when
> >> benchmarking the PV drivers of Xen. This issue appeared with a patch
> >> that addresses security issue XSA-391 (see Fixes below). On an iperf
> >> benchmark, spurious interrupts can represent up to 50% of the
> >> interrupts.
> >
> >If this is the correct fix, near-identical fixes are needed for *all*
> >of the Xen front-ends. Xen virtual block-devices and Xen PCI-passthrough
> >devices are also effected by a similar issue.
> >
> blkfront doesn't call the response handle from multiple places. It
> doesn't seem to be affected by this problem.
> And pcifront neither.
Ick. I had hope it might be a single bug, or at worst a group of
highly similar bugs. This may be several distinct bugs then. :-(
When this bug was first reportted to xen-devel@, I noticed reports of
spurious interrupts on the block backend. Due to a piece of hardware
intended for pass-through, I now know it manifests on the PCI backend
too.
Perhaps you hadn't noticed due to caching lessening the impact of
spurious events on virtual block devices? Whatever the case
`ls /sys/devices/??*-[0-9]*-[0-9]*/xenbus/spurious_events` shows
spurious interrupts on pretty well every virtual device for me (I plan to
test the fix for net-front in the near future).
> >Thanks for finding a candidate fix, this effects many other people who
> >have been troubled by this performance issue.
> >
> >FreeBSD will also need a similar fix.
>
> In FreeBSD, netfront may also be affected.
> xn_assemble_tx_request calls xn_txeof.
> blkfront and pcifront seems good.
Interestingly the problem doesn't seem nearly as severe on ARM.
--
(\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/)
\BS ( | ehem+sigmsg@m5p.com PGP 87145445 | ) /
\_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
next prev parent reply other threads:[~2025-07-11 21:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 16:11 [PATCH] xen/netfront: Fix TX response spurious interrupts Anthoine Bourgeois
2025-07-10 20:05 ` Elliott Mitchell
2025-07-11 7:41 ` Anthoine Bourgeois
2025-07-11 21:22 ` Elliott Mitchell [this message]
2025-07-11 9:29 ` Teddy Astie
2025-07-11 15:27 ` Jürgen Groß
2025-07-11 15:28 ` Jürgen Groß
2025-07-11 15:33 ` Juergen Gross
2025-07-14 7:11 ` Anthoine Bourgeois
2025-07-15 0:37 ` Elliott Mitchell
2025-07-15 8:21 ` Anthoine Bourgeois
2025-07-15 19:19 ` Elliott Mitchell
2025-07-16 7:47 ` Anthoine Bourgeois
2025-07-16 18:31 ` Elliott Mitchell
2025-07-18 20:48 ` Elliott Mitchell
2025-07-21 9:51 ` Anthoine Bourgeois
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=aHGAjJtz66pRBWsM@mattapan.m5p.com \
--to=ehem+xen@m5p.com \
--cc=andrei.semenov@vates.tech \
--cc=anthoine.bourgeois@vates.tech \
--cc=jgross@suse.com \
--cc=oleksandr_tyshchenko@epam.com \
--cc=roger.pau@citrix.com \
--cc=sstabellini@kernel.org \
--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.