[dpdk-stable] vhost: many vhost user ports (backporting to v16.11)

[Stokes, Ian]

> -----Original Message-----
> From: Gray, Mark D
> Sent: Thursday, February 23, 2017 2:57 PM
> To: Yuanhan Liu <yuanhan.liu at linux.intel.com>
> Cc: Wojciechowicz, RobertX <robertx.wojciechowicz at intel.com>;
> stable at dpdk.org; Mcnamara, John <john.mcnamara at intel.com>; Devlin,
> Michelle <michelle.devlin at intel.com>; Weglicki, MichalX
> <michalx.weglicki at intel.com>; Thomas Monjalon <thomas.monjalon at 6wind.com>;
> Stokes, Ian <ian.stokes at intel.com>
> Subject: RE: [dpdk-stable] vhost: many vhost user ports (backporting to
> v16.11)
> 
> 
> 
> > -----Original Message-----
> > From: Yuanhan Liu [mailto:yuanhan.liu at linux.intel.com]
> > Sent: Thursday, February 23, 2017 3:51 AM
> > To: Gray, Mark D <mark.d.gray at intel.com>
> > Cc: Wojciechowicz, RobertX <robertx.wojciechowicz at intel.com>;
> > stable at dpdk.org; Mcnamara, John <john.mcnamara at intel.com>; Devlin,
> > Michelle <michelle.devlin at intel.com>; Weglicki, MichalX
> > <michalx.weglicki at intel.com>; Thomas Monjalon
> > <thomas.monjalon at 6wind.com>; Stokes, Ian <ian.stokes at intel.com>
> > Subject: Re: [dpdk-stable] vhost: many vhost user ports (backporting
> > to
> > v16.11)
> >
> > On Wed, Feb 22, 2017 at 03:28:19PM +0000, Gray, Mark D wrote:
> > >
> > >
> > > > -----Original Message-----
> > > > From: Yuanhan Liu [mailto:yuanhan.liu at linux.intel.com]
> > > > Sent: Wednesday, February 15, 2017 1:19 AM
> > > > To: Gray, Mark D <mark.d.gray at intel.com>
> > > > Cc: Wojciechowicz, RobertX <robertx.wojciechowicz at intel.com>;
> > > > stable at dpdk.org; Mcnamara, John <john.mcnamara at intel.com>; Devlin,
> > > > Michelle <michelle.devlin at intel.com>; Weglicki, MichalX
> > > > <michalx.weglicki at intel.com>; Thomas Monjalon
> > > > <thomas.monjalon at 6wind.com>
> > > > Subject: Re: [dpdk-stable] vhost: many vhost user ports
> > > > (backporting to
> > > > v16.11)
> > > >
> > > > On Tue, Feb 14, 2017 at 09:19:33AM +0000, Gray, Mark D wrote:
> > > > >
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Wojciechowicz, RobertX
> > > > > > Sent: Tuesday, February 14, 2017 8:51 AM
> > > > > > To: Yuanhan Liu <yuanhan.liu at linux.intel.com>; Gray, Mark D
> > > > > > <mark.d.gray at intel.com>
> > > > > > Cc: stable at dpdk.org; Mcnamara, John <john.mcnamara at intel.com>;
> > > > > > Devlin, Michelle <michelle.devlin at intel.com>; Weglicki,
> > > > > > MichalX <michalx.weglicki at intel.com>; Thomas Monjalon
> > > > > > <thomas.monjalon at 6wind.com>
> > > > > > Subject: RE: [dpdk-stable] vhost: many vhost user ports
> > > > > > (backporting to
> > > > > > v16.11)
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > > > It is also worth pointing out that OVS 2.7 will use 16.11
> > > > > > >
> > > > > > > One question though: will they use v16.11.1 or something like
> that?
> > > > > >
> > > > > > @Mark do you know what exactly version OVS is going to use?
> > > > > >
> > > > >
> > > > > We could specify what version to compile against in the
> documentation.
> > > > OVS has a stable branch for 2.7 so we could update the
> > > > documentation if we needed to use a specific tag/branch. In DPDK,
> > > > does each stable release get tagged?
> > > >
> > > > Yes, but the stable tree is located at
> > > >
> > > >     http://dpdk.org/browse/dpdk-stable/
> > > >
> > > > 	--yliu
> > >
> > > Thanks, Ian updated the ovs docs to reflect this. Thanks, this
> > > stable branch
> > really helps us.
> > >
> > > https://mail.openvswitch.org/pipermail/ovs-dev/2017-February/328914.
> > > ht
> > > ml
> >
> > JFYI, the link address changes every time we make a release, something
> > like:
> >
> >     http://fast.dpdk.org/rel/dpdk-16.11.1.tar.xz
> >     http://fast.dpdk.org/rel/dpdk-16.11.2.tar.xz
> >     ...
> >
> > And v16.11.1 is liekly to be released next week.
> >
> > 	--yliu
> 
> I think this is probably OK as we would want to be up to date. The whole
> point of LTS is that it is "stable" and we don't want to have to modify
> the OVS code/docs for each release. However, we will see what the
> community thinks.

I'll raise this at the community call this afternoon for feedback.

Ian