From: "Stokes, Ian" <ian.stokes@intel.com>
To: "Gray, Mark D" <mark.d.gray@intel.com>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: "Wojciechowicz, RobertX" <robertx.wojciechowicz@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Devlin, Michelle" <michelle.devlin@intel.com>,
"Weglicki, MichalX" <michalx.weglicki@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-stable] vhost: many vhost user ports (backporting to v16.11)
Date: Thu, 23 Feb 2017 14:57:39 +0000 [thread overview]
Message-ID: <CD7C01071941AC429549C17338DB8A5289067A0E@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <738D45BC1F695740A983F43CFE1B7EA94E93E804@IRSMSX108.ger.corp.intel.com>
> -----Original Message-----
> From: Gray, Mark D
> Sent: Thursday, February 23, 2017 2:57 PM
> To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
> Cc: Wojciechowicz, RobertX <robertx.wojciechowicz@intel.com>;
> stable@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>; Devlin,
> Michelle <michelle.devlin@intel.com>; Weglicki, MichalX
> <michalx.weglicki@intel.com>; Thomas Monjalon <thomas.monjalon@6wind.com>;
> Stokes, Ian <ian.stokes@intel.com>
> Subject: RE: [dpdk-stable] vhost: many vhost user ports (backporting to
> v16.11)
>
>
>
> > -----Original Message-----
> > From: Yuanhan Liu [mailto:yuanhan.liu@linux.intel.com]
> > Sent: Thursday, February 23, 2017 3:51 AM
> > To: Gray, Mark D <mark.d.gray@intel.com>
> > Cc: Wojciechowicz, RobertX <robertx.wojciechowicz@intel.com>;
> > stable@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>; Devlin,
> > Michelle <michelle.devlin@intel.com>; Weglicki, MichalX
> > <michalx.weglicki@intel.com>; Thomas Monjalon
> > <thomas.monjalon@6wind.com>; Stokes, Ian <ian.stokes@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@linux.intel.com]
> > > > Sent: Wednesday, February 15, 2017 1:19 AM
> > > > To: Gray, Mark D <mark.d.gray@intel.com>
> > > > Cc: Wojciechowicz, RobertX <robertx.wojciechowicz@intel.com>;
> > > > stable@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>; Devlin,
> > > > Michelle <michelle.devlin@intel.com>; Weglicki, MichalX
> > > > <michalx.weglicki@intel.com>; Thomas Monjalon
> > > > <thomas.monjalon@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@linux.intel.com>; Gray, Mark D
> > > > > > <mark.d.gray@intel.com>
> > > > > > Cc: stable@dpdk.org; Mcnamara, John <john.mcnamara@intel.com>;
> > > > > > Devlin, Michelle <michelle.devlin@intel.com>; Weglicki,
> > > > > > MichalX <michalx.weglicki@intel.com>; Thomas Monjalon
> > > > > > <thomas.monjalon@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
prev parent reply other threads:[~2017-02-23 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 12:56 Robert Wojciechowicz
2017-02-14 2:41 ` Yuanhan Liu
2017-02-14 8:50 ` Wojciechowicz, RobertX
2017-02-14 9:19 ` Gray, Mark D
2017-02-15 1:19 ` Yuanhan Liu
2017-02-15 14:57 ` Gray, Mark D
2017-02-22 15:28 ` Gray, Mark D
2017-02-23 3:51 ` Yuanhan Liu
2017-02-23 14:56 ` Gray, Mark D
2017-02-23 14:57 ` Stokes, Ian [this message]
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=CD7C01071941AC429549C17338DB8A5289067A0E@IRSMSX101.ger.corp.intel.com \
--to=ian.stokes@intel.com \
--cc=john.mcnamara@intel.com \
--cc=mark.d.gray@intel.com \
--cc=michalx.weglicki@intel.com \
--cc=michelle.devlin@intel.com \
--cc=robertx.wojciechowicz@intel.com \
--cc=stable@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=yuanhan.liu@linux.intel.com \
/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).