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 RSS support for NVIDIA Mellanox ConnectX-6 Ethernet Adapter Cards
Date: Mon, 29 Mar 2021 12:33:58 +0800	[thread overview]
Message-ID: <CAOJPZgnLjr6VHvtv9NnemxFagvL-k1wrRsB1f1Pq+9qbtPWw0g@mail.gmail.com> (raw)

Hi borisp, saeedm

     I have seen mlx5 driver in 5.12.0-rc4 kernel, then find that
mlx5e_set_rss_hash_opt only support tcp4/udp4/tcp6/udp6. So mlx5
kernel driver doesn't support esp4 rss? Then do you have any plan to
support esp4 or other latest mlx5 driver have supported esp4? Then
does NVIDIA Mellanox ConnectX-6 Ethernet Adapter Cards support esp4
rss in hardware?

static int mlx5e_set_rss_hash_opt(struct mlx5e_priv *priv,
                 struct ethtool_rxnfc *nfc)
{
    int inlen = MLX5_ST_SZ_BYTES(modify_tir_in);
    enum mlx5e_traffic_types tt;
    u8 rx_hash_field = 0;
    void *in;
    tt = flow_type_to_traffic_type(nfc->flow_type);
    if (tt == MLX5E_NUM_INDIR_TIRS)
        return -EINVAL;
    /* RSS does not support anything other than hashing to queues
     * on src IP, dest IP, TCP/UDP src port and TCP/UDP dest
     * port.
     */
    if (nfc->flow_type != TCP_V4_FLOW &&
      nfc->flow_type != TCP_V6_FLOW &&
      nfc->flow_type != UDP_V4_FLOW &&
      nfc->flow_type != UDP_V6_FLOW)
        return -EOPNOTSUPP;

Best Regards,
Junhao

             reply	other threads:[~2021-03-29  4:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29  4:33 高钧浩 [this message]
2021-03-29 20:56 ` ESP RSS support for NVIDIA Mellanox ConnectX-6 Ethernet Adapter Cards Saeed Mahameed
2021-03-30  6:29   ` 高钧浩

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=CAOJPZgnLjr6VHvtv9NnemxFagvL-k1wrRsB1f1Pq+9qbtPWw0g@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.