DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
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: Sat, 28 Nov 2020 09:40:55 -0800
Message-ID: <20201128094055.23882e61@hermes.local> (raw)
In-Reply-To: <15404332.k47CZtomYU@thomas>

On Tue, 06 Oct 2020 00:41:55 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:

> 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?

This needs more discussion. Netvsc PMD does not support rte_flow because
there is not a good/complete implementation of rte_flow library in pure
software form. It might be possible using the BPF stuff that tap supports.

I do not know of anybody who is using vdev_netvsc/failsafe with rte_flow.
Part of the problem is that the TAP implementation of rte_flow supports
a much smaller subset of features than the VF device (MLX).


  parent reply	other threads:[~2020-11-28 17:41 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
2020-11-27 14:01         ` Thomas Monjalon
2020-11-28 17:40         ` Stephen Hemminger [this message]
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=20201128094055.23882e61@hermes.local \
    --to=stephen@networkplumber.org \
    --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=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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git