From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, matan@nvidia.com, asafp@nvidia.com,
shys@nvidia.com, "K. Y. Srinivasan" <kys@microsoft.com>,
Madhan Sivakumar <madhans@microsoft.com>
Subject: Re: [dpdk-dev] [PATCH 1/3] MAINTAINERS remove experimental tag from vdev_netvsc
Date: Tue, 06 Oct 2020 00:41:55 +0200 [thread overview]
Message-ID: <15404332.k47CZtomYU@thomas> (raw)
In-Reply-To: <20200915074705.2fa9cb4a@hermes.lan>
15/09/2020 16:47, Stephen Hemminger:
> Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> > On 9/15/2020 3:03 AM, Stephen Hemminger wrote:
> > > Vdev_netvsc has been around for several years. It no longer needs
> > > to be marked experimental.
> > >
> > > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > > ---
> > > -Microsoft vdev_netvsc - EXPERIMENTAL
> > > +Microsoft vdev_netvsc
> > > M: Matan Azrad <matan@mellanox.com>
> > > F: drivers/net/vdev_netvsc/
> > > F: doc/guides/nics/vdev_netvsc.rst
> >
> > As far as I remember 'vdev_netvsc' was interim solution until 'netvsc'
> > was ready. In this patchset 'netvsc' is also becoming mature.
> >
> > Wouldn't be easier to keep 'vdev_netvsc' experimental to be able to
> > remove it soon?
>
> Let me discuss with Long Li and management.
> Maybe replace EXPERIMENTAL with DEPRECATED in 20.11.
Would be strange to switch from experimental to deprecated :)
+Cc Matan
I think you still need this platform driver (with failsafe and tap)
in case you need rte_flow. Or is it well supported with netvsc PMD?
next prev parent reply other threads:[~2020-10-05 22:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 2:03 [dpdk-dev] [PATCH 0/3] MAINTAINERS changes related to netvsc Stephen Hemminger
2020-09-15 2:03 ` [dpdk-dev] [PATCH 1/3] MAINTAINERS remove experimental tag from vdev_netvsc Stephen Hemminger
2020-09-15 9:42 ` Ferruh Yigit
2020-09-15 14:47 ` Stephen Hemminger
2020-10-05 22:41 ` Thomas Monjalon [this message]
2020-11-27 14:01 ` Thomas Monjalon
2020-11-28 17:40 ` Stephen Hemminger
2020-09-15 2:03 ` [dpdk-dev] [PATCH 2/3] MAINTAINERS - drop Kys and Haiyang Stephen Hemminger
2020-09-15 2:03 ` [dpdk-dev] [PATCH 3/3] MAINTAINERS - remove expermental tag of netvsd PMD Stephen Hemminger
2020-11-27 14:03 ` [dpdk-dev] [PATCH 0/3] MAINTAINERS changes related to netvsc 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=15404332.k47CZtomYU@thomas \
--to=thomas@monjalon.net \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=kys@microsoft.com \
--cc=madhans@microsoft.com \
--cc=matan@nvidia.com \
--cc=shys@nvidia.com \
--cc=stephen@networkplumber.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.