From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
"Kinsella, Ray" <mdr@ashroe.eu>,
Thomas Monjalon <thomas@monjalon.net>
Cc: <matan@nvidia.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ethdev: promote port ownership API as stable
Date: Thu, 2 Jun 2022 12:43:48 +0100 [thread overview]
Message-ID: <c1833a42-0b9a-24f2-175c-6abe7e4f464c@xilinx.com> (raw)
In-Reply-To: <6810e623-a857-5581-55ac-135ff47c261f@oktetlabs.ru>
On 10/28/2021 9:55 AM, Andrew Rybchenko wrote:
> On 10/28/21 11:37 AM, Kinsella, Ray wrote:
>>
>>
>> On 28/10/2021 09:34, Thomas Monjalon wrote:
>>> The port ownership concept was introduced in ethdev in DPDK 18.02.
>>> Not sure it is used by applications except those using failsafe or
>>> netvsc.
>>> It can also be used by libraries or applications to sort out
>>> how ports are controlled.
>>>
>>> Hiding sub-ports controlled by failsafe or netvsc look to be enough
>>> justification to promote this API as stable.
>>>
>>> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>>> ---
>>> doc/guides/prog_guide/poll_mode_drv.rst | 6 +++++-
>>> lib/ethdev/rte_ethdev.h | 20 --------------------
>>> lib/ethdev/version.map | 12 +++++-------
>>> 3 files changed, 10 insertions(+), 28 deletions(-)
>>
>> Acked-by: Ray Kinsella <mdr@ashroe.eu>
>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2022-06-02 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 8:34 Thomas Monjalon
2021-10-28 8:37 ` Kinsella, Ray
2021-10-28 8:55 ` Andrew Rybchenko
2022-06-02 11:43 ` Ferruh Yigit [this message]
2021-10-28 10:22 ` Ferruh Yigit
2021-10-28 10:38 ` Thomas Monjalon
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=c1833a42-0b9a-24f2-175c-6abe7e4f464c@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=mdr@ashroe.eu \
--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).