DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@mellanox.com>
To: Dekel Peled <dekelp@mellanox.com>,
	Matan Azrad <matan@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: prefer DevX API to create Rx objects
Date: Tue, 12 May 2020 11:15:03 +0000	[thread overview]
Message-ID: <AM0PR05MB6707BBFA67FC6E7CBC51FB54C2BE0@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <ecb4c931dd3264f0fe0b48de76a0bd00e9593bea.1589109437.git.dekelp@mellanox.com>

Hi,

> -----Original Message-----
> From: Dekel Peled <dekelp@mellanox.com>
> Sent: Sunday, May 10, 2020 2:19 PM
> To: Matan Azrad <matan@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>; Raslan Darawsheh <rasland@mellanox.com>
> Cc: dev@dpdk.org
> Subject: [PATCH] net/mlx5: prefer DevX API to create Rx objects
> 
> Currently, DevX API is used to create Rx objects (RQ, RQT, TIR) only
> if LRO or hairpin features are enabled on this RQ.
> 
> This patch uses DevX API by default, if DevX is supported and can be
> used. Otherwise, Verbs API is used.
> 
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> Acked-by: Matan Azrad <matan@mellanox.com>
> ---
>  drivers/net/mlx5/mlx5_trigger.c | 14 ++++----------
>  1 file changed, 4 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_trigger.c
> b/drivers/net/mlx5/mlx5_trigger.c
> index feb9154..8d53648 100644
> --- a/drivers/net/mlx5/mlx5_trigger.c
> +++ b/drivers/net/mlx5/mlx5_trigger.c
> @@ -107,17 +107,11 @@
>  	struct mlx5_priv *priv = dev->data->dev_private;
>  	unsigned int i;
>  	int ret = 0;
> -	enum mlx5_rxq_obj_type obj_type = MLX5_RXQ_OBJ_TYPE_IBV;
> -	struct mlx5_rxq_data *rxq = NULL;
> +	enum mlx5_rxq_obj_type obj_type =
> +			priv->config.dv_flow_en && priv->config.devx &&
> +			priv->config.dest_tir ?
> +			MLX5_RXQ_OBJ_TYPE_DEVX_RQ :
> MLX5_RXQ_OBJ_TYPE_IBV;
> 
> -	for (i = 0; i < priv->rxqs_n; ++i) {
> -		rxq = (*priv->rxqs)[i];
> -
> -		if (rxq && rxq->lro) {
> -			obj_type =  MLX5_RXQ_OBJ_TYPE_DEVX_RQ;
> -			break;
> -		}
> -	}
>  	/* Allocate/reuse/resize mempool for Multi-Packet RQ. */
>  	if (mlx5_mprq_alloc_mp(dev)) {
>  		/* Should not release Rx queues but return immediately. */
> --
> 1.8.3.1


Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2020-05-12 11:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-10 11:18 Dekel Peled
2020-05-12 11:15 ` 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=AM0PR05MB6707BBFA67FC6E7CBC51FB54C2BE0@AM0PR05MB6707.eurprd05.prod.outlook.com \
    --to=rasland@mellanox.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=matan@mellanox.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).