All of lore.kernel.org
 help / color / mirror / Atom feed
From: 高钧浩 <gaojunhao0504@gmail.com>
To: borisp@nvidia.com, saeedm@nvidia.com
Cc: netdev@vger.kernel.org, seven.wen@ucloud.cn, junhao.gao@ucloud.cn
Subject: esp-hw-offload support for VF of NVIDIA Mellanox ConnectX-6 Ethernet Adapter Cards
Date: Mon, 29 Mar 2021 16:42:27 +0800	[thread overview]
Message-ID: <CAOJPZgkLvkhN4+_OCLPyWBiXPRc=qLYa3b5jyz63dkn7GQA2Uw@mail.gmail.com> (raw)

Hi Boris,Saeed

     I'm enabling esp-hw-offload for VF of NVIDIA Mellanox ConnectX-6
Ethernet Adapter Cards, but it doesn't work.
     Before I created VF, the esp-hw-offload function of CX-6 is on,
after I created VF, the esp-hw-offload function of VF doesn't inherit
the esp-hw-offload function of CX-6.
     Enable esp-hw-offload could refer to
https://docs.mellanox.com/display/OFEDv522200/IPsec+Crypto+Offload.

     Create VF steps as follows:
     modprobe mlx5_core
     echo 2 > /sys/class/net/net2/device/sriov_numvfs
     # lspci to get pci bdf number(example:0000:07:00.0)
     lspci -nn | grep Mellanox
     echo 0000:07:00.2 > /sys/bus/pci/drivers/mlx5_core/unbind
     echo 0000:07:00.3 > /sys/bus/pci/drivers/mlx5_core/unbind
     /etc/init.d/mst start
     mcra /dev/mst/mt4119_pciconf0  0x31500.17  0
     devlink dev eswitch set pci/0000:07:00.0  mode switchdev encap enable
     echo 0000:07:00.2 > /sys/bus/pci/drivers/mlx5_core/bind
     echo 0000:07:00.3 > /sys/bus/pci/drivers/mlx5_core/bind

     Then query the esp-hw-offload of VF:
     #firstly need to find the created VF(has the properties:
     bus-info: 0000:07:00.2, driver: mlx5_core)
     ethtool -i eth0 | grep esp-hw-offload
     esp-hw-offload: off [fixed]

Best Regards,
Junhao

             reply	other threads:[~2021-03-29  8:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  8:42 高钧浩 [this message]
2021-03-29 21:05 ` esp-hw-offload support for VF of NVIDIA Mellanox ConnectX-6 Ethernet Adapter Cards Saeed Mahameed
2021-04-06  7:44   ` 高钧浩

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='CAOJPZgkLvkhN4+_OCLPyWBiXPRc=qLYa3b5jyz63dkn7GQA2Uw@mail.gmail.com' \
    --to=gaojunhao0504@gmail.com \
    --cc=borisp@nvidia.com \
    --cc=junhao.gao@ucloud.cn \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=seven.wen@ucloud.cn \
    /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.