DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix vector receive check
Date: Tue, 19 Nov 2019 15:16:44 -0800	[thread overview]
Message-ID: <CACZ4nhv2kKF+hFuLB5R8wWvJrL2HJKBK6RzQcfu7TWcGRQvWSA@mail.gmail.com> (raw)
In-Reply-To: <20191119221215.3275-1-lance.richardson@broadcom.com>

On Tue, Nov 19, 2019 at 2:12 PM Lance Richardson <
lance.richardson@broadcom.com> wrote:

> Take DEV_RX_OFFLOAD_RSS_HASH into account when deciding whether vector
> mode receive can be enabled.
>
> Fixes: 8b945a7f7dcb ("drivers/net: update Rx RSS hash offload
> capabilities")
> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
> Reviewed-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
>
Patch applied to dpdk-next-net-brcm. Thanks


> ---
>  drivers/net/bnxt/bnxt_ethdev.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/bnxt/bnxt_ethdev.c
> b/drivers/net/bnxt/bnxt_ethdev.c
> index b1e831b87..41848f36f 100644
> --- a/drivers/net/bnxt/bnxt_ethdev.c
> +++ b/drivers/net/bnxt/bnxt_ethdev.c
> @@ -758,6 +758,7 @@ bnxt_receive_function(__rte_unused struct rte_eth_dev
> *eth_dev)
>                 DEV_RX_OFFLOAD_UDP_CKSUM |
>                 DEV_RX_OFFLOAD_TCP_CKSUM |
>                 DEV_RX_OFFLOAD_OUTER_IPV4_CKSUM |
> +               DEV_RX_OFFLOAD_RSS_HASH |
>                 DEV_RX_OFFLOAD_VLAN_FILTER))) {
>                 PMD_DRV_LOG(INFO, "Using vector mode receive for port
> %d\n",
>                             eth_dev->data->port_id);
> --
> 2.17.1
>
>

      reply	other threads:[~2019-11-19 23:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19 22:12 Lance Richardson
2019-11-19 23:16 ` Ajit Khaparde [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=CACZ4nhv2kKF+hFuLB5R8wWvJrL2HJKBK6RzQcfu7TWcGRQvWSA@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=lance.richardson@broadcom.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).