From: Andrew Lunn <andrew@lunn.ch>
To: Jacky Chou <jacky_chou@aspeedtech.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 回覆: [PATCH] net: ftgmac100: Enable TX interrupt to avoid TX timeout
Date: Fri, 6 Sep 2024 13:48:22 +0200 [thread overview]
Message-ID: <18cfef9e-2ae7-44b6-bfd6-2fe0bba7fbb5@lunn.ch> (raw)
In-Reply-To: <SEYPR06MB51345FBC0146F1517B36584B9D9E2@SEYPR06MB5134.apcprd06.prod.outlook.com>
On Fri, Sep 06, 2024 at 01:57:56AM +0000, Jacky Chou wrote:
> Hello,
>
> When I am verifying iperf3 over UDP, the network hangs.
> Like the log below.
>
> root# iperf3 -c 192.168.100.100 -i1 -t10 -u -b0
> Connecting to host 192.168.100.100, port 5201
> [ 4] local 192.168.100.101 port 35773 connected to 192.168.100.100 port 5201
> [ ID] Interval Transfer Bandwidth Total Datagrams
> [ 4] 0.00-20.42 sec 160 KBytes 64.2 Kbits/sec 20
> [ 4] 20.42-20.42 sec 0.00 Bytes 0.00 bits/sec 0
> [ 4] 20.42-20.42 sec 0.00 Bytes 0.00 bits/sec 0
> [ 4] 20.42-20.42 sec 0.00 Bytes 0.00 bits/sec 0
> [ 4] 20.42-20.42 sec 0.00 Bytes 0.00 bits/sec 0
> [ 4] 20.42-20.42 sec 0.00 Bytes 0.00 bits/sec 0
> [ 4] 20.42-20.42 sec 0.00 Bytes 0.00 bits/sec 0
> [ 4] 20.42-20.42 sec 0.00 Bytes 0.00 bits/sec 0
> [ 4] 20.42-20.42 sec 0.00 Bytes 0.00 bits/sec 0
> [ 4] 20.42-20.42 sec 0.00 Bytes 0.00 bits/sec 0
> - - - - - - - - - - - - - - - - - - - - - - - - -
> [ ID] Interval Transfer Bandwidth Jitter Lost/Total
> Datagrams
> [ 4] 0.00-20.42 sec 160 KBytes 64.2 Kbits/sec 0.000 ms 0/20 (0%)
> [ 4] Sent 20 datagrams
> iperf3: error - the server has terminated The network topology is FTGMAC
> connects directly to a PC. UDP does not need to wait for ACK, unlike TCP.
> Therefore, FTGMAC needs to enable TX interrupt to release TX resources instead
> of waiting for the RX interrupt.
Please don't top post.
So this does seem like a fix. Please read through:
https://www.kernel.org/doc/html/latest/process/maintainer-netdev.html
You need a Fixes: tag, CC: stable tag, use the correct tree, etc.
Andrew
---
pw-bot: cr
next prev parent reply other threads:[~2024-09-06 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 10:31 Jacky Chou
2024-09-05 20:50 ` Andrew Lunn
[not found] ` <SEYPR06MB51345FBC0146F1517B36584B9D9E2@SEYPR06MB5134.apcprd06.prod.outlook.com>
2024-09-06 11:48 ` Andrew Lunn [this message]
2024-09-05 21:47 ` Jakub Kicinski
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=18cfef9e-2ae7-44b6-bfd6-2fe0bba7fbb5@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jacky_chou@aspeedtech.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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
all inboxes | Powered by JetHome®