From: Ray Kinsella <mdr@ashroe.eu>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
David Marchand <david.marchand@redhat.com>
Cc: Raslan Darawsheh <rasland@mellanox.com>,
Ophir Munk <ophirmu@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>,
Matan Azrad <matan@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>,
Olga Shern <olgas@mellanox.com>, Asaf Penso <asafp@mellanox.com>,
"Kinsella, Ray" <ray.kinsella@intel.com>,
Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [dpdk-dev] [PATCH v1] common/mlx5: remove devx depndency on ibv and dv
Date: Thu, 9 Apr 2020 07:21:14 +0100 [thread overview]
Message-ID: <129d14ad-fd5e-8d7c-b832-712ea2891237@ashroe.eu> (raw)
In-Reply-To: <6aef6e5c-143e-8ab1-fceb-3ce690342c06@intel.com>
On 08/04/2020 18:10, Ferruh Yigit wrote:
> On 4/1/2020 10:59 AM, Raslan Darawsheh wrote:
>> 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,
>>
>
> Hi David,
>
> This patch is failing in the travis for ABI checks [1], since mlx has APIs now
> [2], are they public APIs or internal ones, and are they part of the ABI policy,
> can you please check this?
>
> @Thomas, please don't pull from next-net until this resolved, since this patch
> is merged into next-net.
>
> Thanks,
> ferruh
>
So these were added in the 20.02 release.
http://inbox.dpdk.org/dev/1579539790-3882-16-git-send-email-matan@mellanox.com/
Assuming that they are public?
They have the appearance of APIs that perhaps should have been added as experimental in 20.02?
>
> [1]
> [C]'function mlx5_devx_obj* mlx5_devx_cmd_create_cq(ibv_context*,
> mlx5_devx_cq_attr*)' at mlx5_devx_cmds.c:1153:1 has some indirect sub-type changes:
> parameter 1 of type 'ibv_context*' changed:
> in pointed to type 'struct ibv_context':
> entity changed from 'struct ibv_context' to 'void'
> type size changed from 2624 to 0 (in bits)
>
> <multiple similar warnings>
>
> [2]
> https://git.dpdk.org/dpdk/tree/drivers/common/mlx5/rte_common_mlx5_version.map?h=v20.02#n6
>
next prev parent reply other threads:[~2020-04-09 6:21 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
2020-04-08 17:10 ` Ferruh Yigit
2020-04-09 6:21 ` Ray Kinsella [this message]
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=129d14ad-fd5e-8d7c-b832-712ea2891237@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=asafp@mellanox.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@mellanox.com \
--cc=nhorman@tuxdriver.com \
--cc=olgas@mellanox.com \
--cc=ophirmu@mellanox.com \
--cc=rasland@mellanox.com \
--cc=ray.kinsella@intel.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).