patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <luca.boccassi@gmail.com>
To: Huisong Li <lihuisong@huawei.com>
Cc: stable@dpdk.org, liuyonglong@huawei.com
Subject: Re: [PATCH 20.11] net/hns3: fix LRO offload to report
Date: Wed, 15 Nov 2023 11:49:06 +0000	[thread overview]
Message-ID: <CAMw=ZnQtjPW3r3nCMBMj=8xYF06-Yy9iyHaYMEA81G1+0RPBEg@mail.gmail.com> (raw)
In-Reply-To: <20231115100539.62098-1-lihuisong@huawei.com>

On Wed, 15 Nov 2023 at 10:05, Huisong Li <lihuisong@huawei.com> wrote:
>
> [upstream commit a4b2c6815abd3e39daca2e2c93334b813e6a0be4]
>
> Some network engines, like part of HIP09, may not support LRO
> offload, but this offload capability is also reported to user.
> So this patch determines whether driver reports this capability
> based on the capabilities from firmware.
>
> In addition, some network engines, like HIP08, always support LRO
> offload and their firmware don't report this capability. So this
> patch has to move getting revision ID codes to earlier stage and set
> default capabilities for these network engines based on revision ID.
>
> Fixes: ab2e2e344163 ("net/hns3: get device capability in primary process")
> Fixes: f5ed7d99cf45 ("net/hns3: extract common function to obtain revision ID")
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> Signed-off-by: Jie Hai <haijie1@huawei.com>
> ---
>  drivers/net/hns3/hns3_cmd.c       | 18 +++++++++--
>  drivers/net/hns3/hns3_cmd.h       |  1 +
>  drivers/net/hns3/hns3_ethdev.c    | 50 +++++++++++++++++++------------
>  drivers/net/hns3/hns3_ethdev.h    |  5 ++++
>  drivers/net/hns3/hns3_ethdev_vf.c | 28 ++++++-----------
>  drivers/net/hns3/hns3_rxtx.c      |  3 ++
>  6 files changed, 65 insertions(+), 40 deletions(-)

Thanks, applied

      reply	other threads:[~2023-11-15 11:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 10:05 Huisong Li
2023-11-15 11:49 ` Luca Boccassi [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='CAMw=ZnQtjPW3r3nCMBMj=8xYF06-Yy9iyHaYMEA81G1+0RPBEg@mail.gmail.com' \
    --to=luca.boccassi@gmail.com \
    --cc=lihuisong@huawei.com \
    --cc=liuyonglong@huawei.com \
    --cc=stable@dpdk.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).