On Thu, Mar 21, 2013 at 5:41 PM, Simon Horman wrote:
> I think that the way that actions are marshalled by execute_* functions
> and then turned into ODP actions using commit_* has worked well for now
> and serves to provide a reasonably minimal set of ODP actions. However
> it is difficult to mak
On Wed, Mar 20, 2013 at 03:31:51PM -0700, Jesse Gross wrote:
> On Wed, Mar 20, 2013 at 6:18 AM, Simon Horman wrote:
> > * Update the order in which actions are committed and thus
> > appear in the datapath such that MPLS actions appear after
> > l3 and l4 (nw and port) actions.
> >
> > In th
On Wed, Mar 20, 2013 at 6:18 AM, Simon Horman wrote:
> * Update the order in which actions are committed and thus
> appear in the datapath such that MPLS actions appear after
> l3 and l4 (nw and port) actions.
>
> In the case where an mpls_push action is present it should ensure
> that l3
* Update the order in which actions are committed and thus
appear in the datapath such that MPLS actions appear after
l3 and l4 (nw and port) actions.
In the case where an mpls_push action is present it should ensure
that l3 and l4 actions occur first, which seems logical as
once a mpls_
On Tue, Mar 19, 2013 at 12:20:51PM -0700, Jesse Gross wrote:
> On Tue, Mar 19, 2013 at 7:57 AM, Simon Horman wrote:
> > On Tue, Mar 19, 2013 at 10:35:40AM +0900, Simon Horman wrote:
> >> On Mon, Mar 18, 2013 at 08:54:49AM -0700, Jesse Gross wrote:
> >> > On Mon, Mar 18, 2013 at 12:37 AM, Simon Hor
On Tue, Mar 19, 2013 at 7:57 AM, Simon Horman wrote:
> On Tue, Mar 19, 2013 at 10:35:40AM +0900, Simon Horman wrote:
>> On Mon, Mar 18, 2013 at 08:54:49AM -0700, Jesse Gross wrote:
>> > On Mon, Mar 18, 2013 at 12:37 AM, Simon Horman wrote:
>> > > * Update the order in which actions are committed
On Tue, Mar 19, 2013 at 10:35:40AM +0900, Simon Horman wrote:
> On Mon, Mar 18, 2013 at 08:54:49AM -0700, Jesse Gross wrote:
> > On Mon, Mar 18, 2013 at 12:37 AM, Simon Horman wrote:
> > > * Update the order in which actions are committed and thus
> > > appear in the datapath such that MPLS acti
On Mon, Mar 18, 2013 at 08:54:49AM -0700, Jesse Gross wrote:
> On Mon, Mar 18, 2013 at 12:37 AM, Simon Horman wrote:
> > * Update the order in which actions are committed and thus
> > appear in the datapath such that MPLS actions appear after
> > l3 and l4 (nw and port) actions.
> >
> > In t
On Mon, Mar 18, 2013 at 12:37 AM, Simon Horman wrote:
> * Update the order in which actions are committed and thus
> appear in the datapath such that MPLS actions appear after
> l3 and l4 (nw and port) actions.
>
> In the case where an mpls_push action is present it should ensure
> that l3
* Update the order in which actions are committed and thus
appear in the datapath such that MPLS actions appear after
l3 and l4 (nw and port) actions.
In the case where an mpls_push action is present it should ensure
that l3 and l4 actions occur first, which seems logical as
once a mpls_
10 matches
Mail list logo