netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Jakub Kicinski <kuba@kernel.org>,
	Anthoine Bourgeois <anthoine.bourgeois@vates.tech>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>,
	Wei Liu <wei.liu@kernel.org>, Paul Durrant <paul@xen.org>,
	xen-devel@lists.xenproject.org, netdev@vger.kernel.org,
	Elliott Mitchell <ehem+xen@m5p.com>
Subject: Re: [PATCH v2] xen/netfront: Fix TX response spurious interrupts
Date: Fri, 18 Jul 2025 09:19:17 +0200	[thread overview]
Message-ID: <4f54ed1a-e265-43db-b4f2-f3c0d3b3dd00@suse.com> (raw)
In-Reply-To: <20250717072951.3bc2122c@kernel.org>


[-- Attachment #1.1.1: Type: text/plain, Size: 1781 bytes --]

On 17.07.25 16:29, Jakub Kicinski wrote:
> On Tue, 15 Jul 2025 16:11:29 +0000 Anthoine Bourgeois wrote:
>> Fixes: b27d47950e48 ("xen/netfront: harden netfront against event channel storms")
> 
> Not entirely sure who you expect to apply this patch, but if networking
> then I wouldn't classify this is a fix. The "regression" happened 4
> years ago. And this patch doesn't seem to be tuning the logic added by
> the cited commit. I think this is an optimization, -next material, and
> therefore there should be no Fixes tag here. You can refer to the commit
> without the tag.

I think in the end it is a fix of the initial xen-netfront.c contribution
(commit 0d160211965b).

I'm fine to change the Fixes: tag and apply the patch via the Xen tree.

> 
>> @@ -849,9 +847,6 @@ static netdev_tx_t xennet_start_xmit(struct sk_buff *skb, struct net_device *dev
>>   	tx_stats->packets++;
>>   	u64_stats_update_end(&tx_stats->syncp);
>>   
>> -	/* Note: It is not safe to access skb after xennet_tx_buf_gc()! */
>> -	xennet_tx_buf_gc(queue);
>> -
>>   	if (!netfront_tx_slot_available(queue))
>>   		netif_tx_stop_queue(netdev_get_tx_queue(dev, queue->id));
> 
> I thought normally reaping completions from the Tx path is done
> to prevent the queue from filling up, when the device-generated
> completions are slow or the queue is short. I say "normally" but
> this is relatively a uncommon thing to do in networking.
> Maybe it's my lack of Xen knowledge but it would be good to add to
> the commit message why these calls where here in the first place.

I guess the reason for this addition is unknown (singular, as the XDP related
one was probably just a copy-and-paste), as it has been there since the first
version of the driver.


Juergen

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3743 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

  reply	other threads:[~2025-07-18  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15 16:11 [PATCH v2] xen/netfront: Fix TX response spurious interrupts Anthoine Bourgeois
2025-07-17 14:29 ` Jakub Kicinski
2025-07-18  7:19   ` Jürgen Groß [this message]
2025-07-18 17:12     ` Jakub Kicinski
2025-07-18  8:10   ` Anthoine Bourgeois
2025-07-23 22:23   ` Elliott Mitchell

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=4f54ed1a-e265-43db-b4f2-f3c0d3b3dd00@suse.com \
    --to=jgross@suse.com \
    --cc=anthoine.bourgeois@vates.tech \
    --cc=ehem+xen@m5p.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=paul@xen.org \
    --cc=sstabellini@kernel.org \
    --cc=wei.liu@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 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).