From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Matan Azrad <matan@mellanox.com>,
dev@dpdk.org, Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH 0/5] netvsc changes for 18.11
Date: Fri, 31 Aug 2018 18:56:22 +0200 [thread overview]
Message-ID: <2804862.VNJHKtu7v1@xps> (raw)
In-Reply-To: <20180831081516.638d4be4@xeon-e3>
31/08/2018 17:15, Stephen Hemminger:
> On Fri, 31 Aug 2018 13:04:18 +0100
> Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
> > On 8/30/2018 11:35 PM, Stephen Hemminger wrote:
> > > These patches are against dpdk-net-next/master because
> > > that is where previous patches have already been merged.
> > >
> > > Stephen Hemminger (5):
> > > bus/vmbus: add devargs support
> > > net/netvsc: allow tuning latency with devargs
> > > net/netvsc: exhausting transmit descriptors is not an error
> > > net/netvsc: implement link state change callback
> > > net/netvsc: integrated VF support
> >
> > A highlevel question, since netvsc PMD is upstreamed, can we remove vdev_netvsc one?
>
> No.
>
> There are some use cases that still need bifurcated model. And also netvsc PMD
> is still in experimental state and vdev_netvsc/failsafe/tap are more stable.
>
> I hope maybe by 19.11?
19.11 would be reasonnable target to deprecate vdev_netvsc.
next prev parent reply other threads:[~2018-08-31 16:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 22:35 Stephen Hemminger
2018-08-30 22:35 ` [dpdk-dev] [PATCH 1/5] bus/vmbus: add devargs support Stephen Hemminger
2018-09-14 12:46 ` Ferruh Yigit
2018-09-14 13:06 ` Gaëtan Rivet
2018-09-14 13:19 ` Ferruh Yigit
2018-09-14 13:58 ` Gaëtan Rivet
2018-09-14 15:21 ` Stephen Hemminger
2018-08-30 22:35 ` [dpdk-dev] [PATCH 2/5] net/netvsc: allow tuning latency with devargs Stephen Hemminger
2018-09-14 12:47 ` Ferruh Yigit
2018-08-30 22:35 ` [dpdk-dev] [PATCH 3/5] net/netvsc: exhausting transmit descriptors is not an error Stephen Hemminger
2018-08-30 22:35 ` [dpdk-dev] [PATCH 4/5] net/netvsc: implement link state change callback Stephen Hemminger
2018-08-31 8:25 ` Gaëtan Rivet
2018-08-31 15:13 ` Stephen Hemminger
2018-08-30 22:35 ` [dpdk-dev] [PATCH 5/5] net/netvsc: integrated VF support Stephen Hemminger
2018-09-14 12:57 ` Ferruh Yigit
2018-09-14 15:22 ` Stephen Hemminger
2018-08-31 12:04 ` [dpdk-dev] [PATCH 0/5] netvsc changes for 18.11 Ferruh Yigit
2018-08-31 15:15 ` Stephen Hemminger
2018-08-31 16:56 ` Thomas Monjalon [this message]
2018-09-14 13:25 ` Ferruh Yigit
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=2804862.VNJHKtu7v1@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=matan@mellanox.com \
--cc=shahafs@mellanox.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 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).