From: Ben Pfaff <blp@nicira.com>
To: Simon Horman <horms@verge.net.au>
Cc: dev@openvswitch.org, netdev@vger.kernel.org,
Jesse Gross <jesse@nicira.com>, Ravi K <rkerur@gmail.com>
Subject: Re: [ovs-dev] [PATCH v2.51 0/5] MPLS actions and matches
Date: Tue, 26 Nov 2013 07:33:47 -0800 [thread overview]
Message-ID: <20131126153347.GA2662@nicira.com> (raw)
In-Reply-To: <20131126080759.GA26597@verge.net.au>
On Tue, Nov 26, 2013 at 05:08:04PM +0900, Simon Horman wrote:
> On Thu, Nov 21, 2013 at 12:46:41PM +0900, Simon Horman wrote:
> > Hi,
> >
> > This series implements MPLS actions and matches based on work by
> > Ravi K, Leo Alterman, Yamahata-san and Joe Stringer.
> >
> > This series provides three changes
> >
> > * Patches 1 - 3
> >
> > Provide user-space support for the VLAN/MPLS tag insertion order
> > up to and including OpenFlow 1.2, and the different ordering
> > specified from OpenFlow 1.3. In a nutshell the datapath always
> > uses the OpenFlow 1.3 ordering, which is to always insert tags
> > immediately after the L2 header, regardless of the presence of other
> > tags. And ovs-vswtichd provides compatibility for the behaviour up
> > to OpenFlow 1.2, which is that MPLS tags should follow VLAN tags
> > if present.
> >
> > Ben, these are for you to review.
>
> Hi Ben,
>
> I wonder if you could find some time to look over these.
>
> I believe that the first patch has not previously been reviewed
> but other than that there should be few areas of excitement.
I'm taking today and the remainder of this week off (Thursday and Friday
are a holiday here in the U.S.), so unfortunately there is not much
chance of progress before Monday.
next prev parent reply other threads:[~2013-11-26 15:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 3:46 [PATCH v2.51 0/5] MPLS actions and matches Simon Horman
[not found] ` <1385005606-30130-1-git-send-email-horms-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2013-11-21 3:46 ` [PATCH v2.51 1/5] ofp-actions: Allow Consistency checking of OF1.3+ VLAN actions after mpls_push Simon Horman
2013-12-04 21:24 ` Ben Pfaff
2013-12-04 23:58 ` Simon Horman
2013-12-05 0:44 ` Ben Pfaff
2013-12-05 0:51 ` Simon Horman
2013-12-05 1:01 ` Ben Pfaff
[not found] ` <20131205010111.GE11354-l0M0P4e3n4LQT0dZR+AlfA@public.gmane.org>
2013-12-05 2:26 ` Simon Horman
2013-12-05 17:56 ` Ben Pfaff
2013-12-06 3:29 ` Simon Horman
[not found] ` <20131206032924.GA20522-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org>
2013-12-06 4:21 ` Ben Pfaff
2013-11-21 3:46 ` [PATCH v2.51 2/5] odp: Allow VLAN actions after MPLS actions Simon Horman
2013-11-21 3:46 ` [PATCH v2.51 3/5] lib: Support pushing of MPLS LSE before or after VLAN tag Simon Horman
2013-11-21 3:46 ` [PATCH v2.51 4/5] datapath: Break out deacceleration portion of vlan_push Simon Horman
2013-11-21 3:46 ` [PATCH v2.51 5/5] datapath: Add basic MPLS support to kernel Simon Horman
2013-11-26 8:08 ` [ovs-dev] [PATCH v2.51 0/5] MPLS actions and matches Simon Horman
2013-11-26 15:33 ` Ben Pfaff [this message]
2013-11-27 0:12 ` Simon Horman
2013-12-04 9:16 ` Simon Horman
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=20131126153347.GA2662@nicira.com \
--to=blp@nicira.com \
--cc=dev@openvswitch.org \
--cc=horms@verge.net.au \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=rkerur@gmail.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).