DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: techboard@dpdk.org, David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, "Xia, Chenbo" <chenbo.xia@intel.com>,
	"Xueming(Steven) Li" <xuemingl@nvidia.com>,
	Xiao Wang <xiao.w.wang@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [dpdk-dev] [PATCH] vhost: mark vDPA driver API as internal
Date: Thu, 28 Oct 2021 15:00:22 +0200	[thread overview]
Message-ID: <77babc7e-bf81-0136-9251-869ea5f68485@redhat.com> (raw)
In-Reply-To: <CAJFAV8z53O0Gr8jrzH96kVsQmEz8OxQtE9genDLDEvgTuMyZJQ@mail.gmail.com>



On 10/28/21 14:38, David Marchand wrote:
> On Thu, Oct 28, 2021 at 2:03 PM Maxime Coquelin
> <maxime.coquelin@redhat.com> wrote:
>>
>> This patch marks the vDPA driver APIs as internal and
>> rename the corresponding header file.
>>
>> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
>> ---
>>   drivers/vdpa/ifc/ifcvf_vdpa.c            |  2 +-
>>   drivers/vdpa/mlx5/mlx5_vdpa.h            |  2 +-
>>   lib/vhost/meson.build                    |  4 +++-
>>   lib/vhost/vdpa.c                         |  2 +-
>>   lib/vhost/{rte_vdpa_dev.h => vdpa_dev.h} |  6 ++++++
> 
> It is more explicit it is a driver-only header if we rename as
> vdpa_driver.h or vdpa_pmd.h.

Agree, I can take the opportunity to rename it to vdpa_driver.h.

> [snip]
> 
>> @@ -86,3 +82,12 @@ EXPERIMENTAL {
>>          rte_vhost_async_channel_unregister_thread_unsafe;
>>          rte_vhost_clear_queue_thread_unsafe;
>>   };
>> +
>> +INTERNAL {
>> +       global;
>> +
>> +       rte_vdpa_register_device;
>> +       rte_vdpa_unregister_device;
>> +       rte_vhost_host_notifier_ctrl;
>> +       rte_vdpa_relay_vring_used;
>> +};
> 
> Alphabetical order, please.

Will do.

> Please also add a note in the release notes.
> 
> Strictly speaking, this is an announced API change.
> Cc: techboard.

Correct, I think we need a vote from the techboard.

@Techboard, this API change felt through the cracks.

Please note that the drivers APIs that are being marked as
internal were already moved in a dedicated header last year,
so any application are likely not using these APIs.
There is a patch for mlx5 vdpa that introduces a new entry
to struct rte_vdpa_dev_ops, so I think it would be better
to have these APIs marked as internal before mlx5 patch is
applied.

Thanks in advance,
Maxime

> 
> The rest lgtm.
> Thanks.
> 


      reply	other threads:[~2021-10-28 13:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28 12:03 Maxime Coquelin
2021-10-28 12:38 ` David Marchand
2021-10-28 13:00   ` Maxime Coquelin [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=77babc7e-bf81-0136-9251-869ea5f68485@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mdr@ashroe.eu \
    --cc=techboard@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=xiao.w.wang@intel.com \
    --cc=xuemingl@nvidia.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).