From: Raslan Darawsheh <rasland@mellanox.com>
To: Ophir Munk <ophirmu@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>,
Matan Azrad <matan@mellanox.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Olga Shern <olgas@mellanox.com>,
Ophir Munk <ophirmu@mellanox.com>,
Asaf Penso <asafp@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH v1] common/mlx5: remove devx depndency on ibv and dv
Date: Wed, 1 Apr 2020 09:59:32 +0000 [thread overview]
Message-ID: <AM0PR05MB6707E113B8AA9610F2430D1EC2C90@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20200329223222.7553-1-ophirmu@mellanox.com>
Hi,
> -----Original Message-----
> From: Ophir Munk <ophirmu@mellanox.com>
> Sent: Monday, March 30, 2020 1:32 AM
> To: dev@dpdk.org; Matan Azrad <matan@mellanox.com>
> Cc: Thomas Monjalon <thomas@monjalon.net>; Olga Shern
> <olgas@mellanox.com>; Raslan Darawsheh <rasland@mellanox.com>; Ophir
> Munk <ophirmu@mellanox.com>; Asaf Penso <asafp@mellanox.com>
> Subject: [PATCH v1] common/mlx5: remove devx depndency on ibv and dv
>
> File mlx5_devx_cmds.c should contain pure DevX calls. It must be OS
> agnostic and not include any references to ibv or dv structs (defined in
> ibverbs and rdma-core linux libraries). This commit replaces all ibv and
> dv references with 'void *'. Specifically, the following struct were
> replaced:
> 1. struct ibv_context *
> 2. struct ibv_qp *
> 3. struct mlx5dv_devx_cmd_comp *
>
> Signed-off-by: Ophir Munk <ophirmu@mellanox.com>
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2020-04-01 9:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 22:32 Ophir Munk
2020-03-31 6:29 ` Matan Azrad
2020-04-01 9:59 ` Raslan Darawsheh [this message]
2020-04-08 17:10 ` Ferruh Yigit
2020-04-09 6:21 ` Ray Kinsella
2020-04-09 7:24 ` David Marchand
2020-04-16 17:35 ` Ferruh Yigit
2020-04-16 20:00 ` Thomas Monjalon
2020-04-17 16:19 ` Ferruh Yigit
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=AM0PR05MB6707E113B8AA9610F2430D1EC2C90@AM0PR05MB6707.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=asafp@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=thomas@monjalon.net \
/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).