From: Chenbo Xia <chenbox@nvidia.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH] vhost: promote max queue setting API to stable
Date: Thu, 10 Oct 2024 01:52:05 +0000 [thread overview]
Message-ID: <DC832FF1-A473-400F-91ED-22E5838408B8@nvidia.com> (raw)
In-Reply-To: <20241009130029.2906449-1-maxime.coquelin@redhat.com>
> On Oct 9, 2024, at 21:00, Maxime Coquelin <maxime.coquelin@redhat.com> wrote:
>
> External email: Use caution opening links or attachments
>
>
> This patch promotes the rte_vhost_driver_set_max_queue_num
> API to stable.
>
> Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> ---
> lib/vhost/rte_vhost.h | 4 ----
> lib/vhost/version.map | 2 +-
> 2 files changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/lib/vhost/rte_vhost.h b/lib/vhost/rte_vhost.h
> index 328281ba0f..0ce3f31cbe 100644
> --- a/lib/vhost/rte_vhost.h
> +++ b/lib/vhost/rte_vhost.h
> @@ -610,9 +610,6 @@ int
> rte_vhost_driver_get_queue_num(const char *path, uint32_t *queue_num);
>
> /**
> - * @warning
> - * @b EXPERIMENTAL: this API may change, or be removed, without prior notice.
> - *
> * Set the maximum number of queue pairs supported by the device.
> * The value set is ignored for Vhost-user backends. It is only taken into
> * account with VDUSE backends.
> @@ -624,7 +621,6 @@ rte_vhost_driver_get_queue_num(const char *path, uint32_t *queue_num);
> * @return
> * 0 on success, -1 on failure
> */
> -__rte_experimental
> int
> rte_vhost_driver_set_max_queue_num(const char *path, uint32_t max_queue_pairs);
>
> diff --git a/lib/vhost/version.map b/lib/vhost/version.map
> index 30bc312262..8333e100ed 100644
> --- a/lib/vhost/version.map
> +++ b/lib/vhost/version.map
> @@ -32,6 +32,7 @@ DPDK_25 {
> rte_vhost_driver_get_vdpa_device;
> rte_vhost_driver_register;
> rte_vhost_driver_set_features;
> + rte_vhost_driver_set_max_queue_num;
> rte_vhost_driver_set_protocol_features;
> rte_vhost_driver_start;
> rte_vhost_driver_unregister;
> @@ -97,7 +98,6 @@ EXPERIMENTAL {
> rte_vhost_async_dma_unconfigure;
>
> # added in 23.07
> - rte_vhost_driver_set_max_queue_num;
> rte_vhost_notify_guest;
> };
>
> —
> 2.46.2
>
Reviewed-by: Chenbo Xia <chenbox@nvidia.com>
next prev parent reply other threads:[~2024-10-10 1:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 13:00 Maxime Coquelin
2024-10-09 15:14 ` Stephen Hemminger
2024-10-10 1:52 ` Chenbo Xia [this message]
2024-10-14 11:47 ` Maxime Coquelin
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=DC832FF1-A473-400F-91ED-22E5838408B8@nvidia.com \
--to=chenbox@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.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).