On Mon, Nov 06, 2017 at 06:42:44PM +0800, Yang, Yi wrote: > On Thu, Nov 02, 2017 at 04:53:15AM +0800, Ben Pfaff wrote: > > On Wed, Aug 30, 2017 at 02:21:01AM +0800, Yi Yang wrote: > > > IETF NSH draft will be approved by end of August, NSH header > > > format has been finalized and won't be change anymore, so we > > > need to follow this final spec to implement nsh. > > > > > > kernel data path also needs finalized uAPIs, they can't be > > > changed once they are merged. > > > > > > This patch adds new nsh key 'ttl', bits of flags and mdtype > > > fields are also changed to follow the final spec. > > > > > > A new action dec_nsh_ttl will be added in the following patch. > > > > > > Signed-off-by: Yi Yang <[email protected]> > > > > It's time to take another look at NSH, by adding support for the latest > > draft. I posted a patch to kick this off: > > > > https://mail.openvswitch.org/pipermail/ovs-dev/2017-November/340365.html > > > > This is the sort of patch that could be backported to 2.8 if that is > > desirable. > > > > After we get the protocol format fixed, I suggest rebasing and reposting > > these patches so that we can get enhanced support into 2.9. > > > > Thanks, > > Ben, no problem, NSH kernel patch will be merged very soon, after that > I'll rework this patch series, netlink message format for OVS_KEY_ATTR_NSH > has big change per kernel requirement, so userspace part will have some > big change for push_nsh and set. action names for data path also need > to be changed. > > We also can start backporting NSH kernel patches to OVS to support > compat mode, this requires to backport many kernel patches before NSH > kernel patch, it will be great if OVS 2.9 can support both userspace and > kernel data path.
Sounds good. _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
