From: Stephen Hemminger <stephen@networkplumber.org>
To: David Christensen <drc@linux.vnet.ibm.com>
Cc: viacheslavo@mellanox.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: txq_inline_min not set for ConnectX-5 adapters
Date: Wed, 31 Jul 2019 15:55:42 -0700 [thread overview]
Message-ID: <20190731155542.44acf845@hermes.lan> (raw)
In-Reply-To: <1564612871-162495-1-git-send-email-drc@linux.vnet.ibm.com>
On Wed, 31 Jul 2019 17:41:11 -0500
David Christensen <drc@linux.vnet.ibm.com> wrote:
> The function mlx5_set_min_inline() includes a switch() that checks
> various PCI device IDs in order to set the txq_inline_min value. No
> value is set when the PCI device ID matches the ConnectX-5 adapters,
> resulting in an assert() failure later in the function
> mlx5_set_txlimit_params().
>
> This error was encountered on an IBM Power 9 system running RHEL 7.6
> w/o Mellanox OFED installed.
>
> Fixes: 38b4b397a57d ("net/mlx5: add Tx configuration and setup")
> Cc: viacheslavo@mellanox.com
>
> Signed-off-by: David Christensen <drc@linux.vnet.ibm.com>
> ---
> drivers/net/mlx5/mlx5.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/mlx5/mlx5.c b/drivers/net/mlx5/mlx5.c
> index 3a345c7..0f61dd5 100644
> --- a/drivers/net/mlx5/mlx5.c
> +++ b/drivers/net/mlx5/mlx5.c
> @@ -1341,6 +1341,7 @@ struct mlx5_dev_spawn_data {
> * and PFC control may be broken, so disable feature.
> */
> config->hw_vlan_insert = 0;
> + config->txq_inline_min = MLX5_INLINE_HSIZE_NONE;
> break;
> default:
> config->txq_inline_min = MLX5_INLINE_HSIZE_NONE;
This is a case where a simple switch fallthrough would have same effect.
next prev parent reply other threads:[~2019-07-31 22:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 22:41 David Christensen
2019-07-31 22:55 ` Stephen Hemminger [this message]
2019-08-01 4:32 ` Slava Ovsiienko
2019-08-01 18:24 ` David Christensen
2019-08-02 3:48 ` Slava Ovsiienko
2019-08-02 18:17 ` David Christensen
2019-08-04 5:34 ` Slava Ovsiienko
2019-08-04 10:53 ` Raslan Darawsheh
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=20190731155542.44acf845@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=viacheslavo@mellanox.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).