From: wenxu <wenxu@ucloud.cn>
To: tariqt@nvidia.com, borisp@nvidia.com
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Ktls RX offload in CX6 of mellanox
Date: Fri, 15 Jan 2021 11:53:47 +0800 [thread overview]
Message-ID: <b0053adc-760e-d3ae-5a88-34bea387aedb@ucloud.cn> (raw)
In-Reply-To: <HE1PR05MB473281BEC529F6705646885DB4480@HE1PR05MB4732.eurprd05.prod.outlook.com>
Hi Mellanox team.
I test the ktls offload feature with CX6 dx with net-next tree.
I found the driver already support the KTLS rx offload function
My firmware version is the latest one 22.29.1016
According to the document:
https://docs.mellanox.com/display/OFEDv521040/Kernel+Transport+Layer+Security+%28kTLS%29+Offloads
With the 22.29.1016 FW, The RX offload is supported now.
# lspci | grep Ether
b3:00.0 Ethernet controller: Mellanox Technologies MT2892 Family [ConnectX-6 Dx]
b3:00.1 Ethernet controller: Mellanox Technologies MT2892 Family [ConnectX-6 Dx]
# ethtool -i net2
driver: mlx5_core
version: 5.0-0
firmware-version: 22.29.1016 (MT_0000000430)
expansion-rom-version:
bus-info: 0000:b3:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: yes
# ethtool -K net2 | grep tls-hw
tls-hw-tx-offload: on
tls-hw-rx-offload: off [fixed]
But I found the RX offload is not supported currently?
I found the mlx5_accel_is_ktls_rx(mdev) will return false and it leads this feature
not supported. So it means the current FW also does not support RX offload?
BR
wenxu
prev parent reply other threads:[~2021-01-15 4:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 8:09 Ktls offload in cx6 of mellanox wenxu
[not found] ` <AM7PR05MB7092681958225E065CAD9174B0480@AM7PR05MB7092.eurprd05.prod.outlook.com>
[not found] ` <HE1PR05MB473281BEC529F6705646885DB4480@HE1PR05MB4732.eurprd05.prod.outlook.com>
2021-01-15 3:53 ` wenxu [this message]
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=b0053adc-760e-d3ae-5a88-34bea387aedb@ucloud.cn \
--to=wenxu@ucloud.cn \
--cc=borisp@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=tariqt@nvidia.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;
as well as URLs for NNTP newsgroup(s).