netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Alexander Duyck <alexander.duyck@gmail.com>, netdev@vger.kernel.org
Cc: linux@armlinux.org.uk, hkallweit1@gmail.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, kuba@kernel.org,
	kernel-team@meta.com, edumazet@google.com
Subject: Re: [net-next PATCH v3 0/8] Add support for 25G, 50G, and 100G to fbnic
Date: Thu, 19 Jun 2025 10:44:41 +0200	[thread overview]
Message-ID: <5ce8c769-6c36-4d0a-831d-e8edab830beb@redhat.com> (raw)
In-Reply-To: <175028434031.625704.17964815932031774402.stgit@ahduyck-xeon-server.home.arpa>

On 6/19/25 12:07 AM, Alexander Duyck wrote:
> The fbnic driver up till now had avoided actually reporting link as the
> phylink setup only supported up to 40G configurations. This changeset is
> meant to start addressing that by adding support for 50G and 100G interface
> types.
> 
> With that basic support added fbnic can then set those types based on the
> EEPROM configuration provided by the firmware and then report those speeds
> out using the information provided via the phylink call for getting the
> link ksettings. This provides the basic MAC support and enables supporting
> the speeds as well as configuring flow control.
> 
> After this I plan to add support for a PHY that will represent the SerDes
> PHY being used to manage the link as we need a way to indicate link
> training into phylink to prevent link flaps on the PCS while the SerDes is
> in training, and then after that I will look at rolling support for our
> PCS/PMA into the XPCS driver.

Apparently this is causing TSO tests failures:

# ok 1 tso.ipv4
# # Testing with mangleid enabled
# # Check| At
/home/virtme/testing-24/tools/testing/selftests/drivers/net/hw/./tso.py,
line 160, in f:
# # Check|     run_one_stream(cfg, ipver, remote_v4, remote_v6,
# # Check| At
/home/virtme/testing-24/tools/testing/selftests/drivers/net/hw/./tso.py,
line 80, in run_one_stream:
# # Check|     ksft_ge(qstat_new['tx-hw-gso-wire-packets'] -
# # Check failed 0 < 2516.0 Number of LSO wire-packets with LSO enabled
# not ok 2 tso.vxlan4_ipv4
# # Check| At
/home/virtme/testing-24/tools/testing/selftests/drivers/net/hw/./tso.py,
line 160, in f:
# # Check|     run_one_stream(cfg, ipver, remote_v4, remote_v6,
# # Check| At
/home/virtme/testing-24/tools/testing/selftests/drivers/net/hw/./tso.py,
line 80, in run_one_stream:
# # Check|     ksft_ge(qstat_new['tx-hw-gso-wire-packets'] -
# # Check failed 0 < 2516.0 Number of LSO wire-packets with LSO enabled
# not ok 3 tso.vxlan4_ipv6

And vlxlan TSO, too:

# # Check| At
/home/virtme/testing-24/tools/testing/selftests/drivers/net/hw/./tso.py,
line 154, in f:
# # Check|     run_one_stream(cfg, ipver, remote_v4, remote_v6,
should_lso=False)
# # Check| At
/home/virtme/testing-24/tools/testing/selftests/drivers/net/hw/./tso.py,
line 65, in run_one_stream:
# # Check|     ksft_lt(tcp_sock_get_retrans(sock), 10)
# # Check failed 10 >= 10
# not ok 10 tso.vxlan6_ipv6

I'm tentatively/blindly removing this from the PW queue to double check
the assumption.

/P


  parent reply	other threads:[~2025-06-19  8:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 22:07 [net-next PATCH v3 0/8] Add support for 25G, 50G, and 100G to fbnic Alexander Duyck
2025-06-18 22:07 ` [net-next PATCH v3 1/8] net: phy: Add interface types for 50G and 100G Alexander Duyck
2025-06-18 22:07 ` [net-next PATCH v3 2/8] fbnic: Do not consider mailbox "initialized" until we have verified fw version Alexander Duyck
2025-06-18 22:07 ` [net-next PATCH v3 3/8] fbnic: Retire "AUTO" flags and cleanup handling of FW link settings Alexander Duyck
2025-06-18 22:07 ` [net-next PATCH v3 4/8] fbnic: Replace link_mode with AUI Alexander Duyck
2025-06-18 22:07 ` [net-next PATCH v3 5/8] fbnic: Update FW link mode values to represent actual link modes Alexander Duyck
2025-06-18 22:07 ` [net-next PATCH v3 6/8] fbnic: Set correct supported modes and speeds based on FW setting Alexander Duyck
2025-06-18 22:08 ` [net-next PATCH v3 7/8] fbnic: Add support for reporting link config Alexander Duyck
2025-06-18 22:08 ` [net-next PATCH v3 8/8] fbnic: Add support for setting/getting pause configuration Alexander Duyck
2025-06-19  8:44 ` Paolo Abeni [this message]
2025-06-19 15:17   ` [net-next PATCH v3 0/8] Add support for 25G, 50G, and 100G to fbnic Jakub Kicinski
2025-06-20 14:36   ` Jakub Kicinski
2025-06-24  7:28     ` Paolo Abeni
2025-06-24  7:50 ` patchwork-bot+netdevbpf

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=5ce8c769-6c36-4d0a-831d-e8edab830beb@redhat.com \
    --to=pabeni@redhat.com \
    --cc=alexander.duyck@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.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).