From: "Anthoine Bourgeois" <anthoine.bourgeois@vates.tech>
To: "Elliott Mitchell" <ehem+xen@m5p.com>
Cc: "Juergen Gross" <jgross@suse.com>,
xen-devel@lists.xenproject.org,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Oleksandr Tyshchenko" <oleksandr_tyshchenko@epam.com>
Subject: Re: [PATCH] xen/netfront: Fix TX response spurious interrupts
Date: Tue, 15 Jul 2025 08:21:40 +0000 [thread overview]
Message-ID: <aHYPktKlOyFJ49bb@mail.vates.tech> (raw)
In-Reply-To: <aHWi3ncNrVBO6jrh@mattapan.m5p.com>
On Mon, Jul 14, 2025 at 05:37:51PM -0700, Elliott Mitchell wrote:
>On Mon, Jul 14, 2025 at 07:11:06AM +0000, Anthoine Bourgeois wrote:
>> On Fri, Jul 11, 2025 at 05:33:43PM +0200, Juergen Gross wrote:
>> >On 10.07.25 18:11, Anthoine Bourgeois wrote:
>
>Tested on a VM which this could be tried on.
>
>Booting was successful, network appeared to function as it had been.
>Spurious events continued to occur at roughly the same interval they had
>been.
>
>I can well believe this increases Xen network performance and may
>reduce the occurrence of spurious interrupts, but it certainly doesn't
>fully fix the problem(s). Appears you're going to need to keep digging.
>
>I believe this does count as Tested-by since I observed no new ill
>effects. Just the existing ill effects aren't fully solved.
>
Thank you for the test!
Could you send me the domU/dom0 kernel version and xen version ?
Regards,
Anthoine
Anthoine Bourgeois | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next prev parent reply other threads:[~2025-07-15 8:21 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
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 [this message]
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=aHYPktKlOyFJ49bb@mail.vates.tech \
--to=anthoine.bourgeois@vates.tech \
--cc=ehem+xen@m5p.com \
--cc=jgross@suse.com \
--cc=oleksandr_tyshchenko@epam.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.