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

Gray, Mark D mark.d.gray at intel.com
Wed Feb 15 15:57:10 CET 2017



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

I didn't realise that this was a different repository. It sounds like we should update the documentation in OVS with this information. We could just point to the stable branch which should catch the most up-to-date bugfixes.


More information about the stable mailing list