From: Raslan Darawsheh <rasland@mellanox.com>
To: Alexander Kozyrev <akozyrev@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Slava Ovsiienko <viacheslavo@mellanox.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: improve logging of MPRQ selection
Date: Tue, 21 Apr 2020 17:56:09 +0000 [thread overview]
Message-ID: <AM0PR05MB67072C1998DD99420653AE51C2D50@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1587144039-24144-1-git-send-email-akozyrev@mellanox.com>
Hi,
> -----Original Message-----
> From: Alexander Kozyrev <akozyrev@mellanox.com>
> Sent: Friday, April 17, 2020 8:21 PM
> To: dev@dpdk.org
> Cc: Raslan Darawsheh <rasland@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>; stable@dpdk.org
> Subject: [PATCH] net/mlx5: improve logging of MPRQ selection
>
> MPRQ is silently turned off in case there is not enough
> Rx queues configured. Improve the logging to show a
> warning in this case to notify a user about the Rx burst
> function selected.
>
> Fixes: 7d6bf6b866b8 ("net/mlx5: add Multi-Packet Rx support")
> Cc: stable@dpdk.org
>
> Signed-off-by: Alexander Kozyrev <akozyrev@mellanox.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---
> drivers/net/mlx5/mlx5_rxq.c | 15 +++++++++------
> 1 file changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/net/mlx5/mlx5_rxq.c b/drivers/net/mlx5/mlx5_rxq.c
> index 9bc7af6..7a50ec6 100644
> --- a/drivers/net/mlx5/mlx5_rxq.c
> +++ b/drivers/net/mlx5/mlx5_rxq.c
> @@ -1921,19 +1921,22 @@ struct mlx5_rxq_ctrl *
> tmpl->rxq.sges_n = sges_n;
> max_lro_size = max_rx_pkt_len;
> }
> - if (mprq_en && !mlx5_rxq_mprq_enabled(&tmpl->rxq))
> + if (config->mprq.enabled && !mlx5_rxq_mprq_enabled(&tmpl-
> >rxq))
> DRV_LOG(WARNING,
> - "port %u MPRQ is requested but cannot be enabled"
> - " (requested: packet size = %u, desc = %u,"
> - " stride_sz = %u, stride_num = %u,"
> - " supported: min_stride_sz = %u, max_stride_sz =
> %u).",
> - dev->data->port_id, non_scatter_min_mbuf_size,
> desc,
> + "port %u MPRQ is requested but cannot be
> enabled\n"
> + " (requested: pkt_sz = %u, desc_num = %u,"
> + " rxq_num = %u, stride_sz = %u, stride_num = %u\n"
> + " supported: min_rxqs_num = %u,"
> + " min_stride_sz = %u, max_stride_sz = %u).",
> + dev->data->port_id, non_scatter_min_mbuf_size,
> + desc, priv->rxqs_n,
> config->mprq.stride_size_n ?
> (1U << config->mprq.stride_size_n) :
> (1U << mprq_stride_size),
> config->mprq.stride_num_n ?
> (1U << config->mprq.stride_num_n) :
> (1U << mprq_stride_nums),
> + config->mprq.min_rxqs_num,
> (1U << config->mprq.min_stride_size_n),
> (1U << config->mprq.max_stride_size_n));
> DRV_LOG(DEBUG, "port %u maximum number of segments per
> packet: %u",
> --
> 1.8.3.1
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-04-21 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-17 17:20 Alexander Kozyrev
2020-04-21 17:56 ` Raslan Darawsheh [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=AM0PR05MB67072C1998DD99420653AE51C2D50@AM0PR05MB6707.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=akozyrev@mellanox.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--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).