On 08/14/14 at 12:43pm, Ben Pfaff wrote:
> On Thu, Aug 14, 2014 at 09:42:13PM +0200, Thomas Graf wrote:
> > On 08/14/14 at 09:22am, Ben Pfaff wrote:
> > > The real issue here is that you'd like to allow OFPACT_REG_MOVE to be
> > > part of an action set. That's fine. I have no objection. The only
> > > task is to decide where reg_move actions go in the ordering. Where do
> > > you want it? I get the impression that you'd like them mixed together
> > > with the "set" actions but maybe that's just because you've been trying
> > > to rationalize them as a form of "set" actions.
> >
> > OK. My preference would be mixed together with the "set" actions so
> > that a move followed by a load to the same register results in the
> > load properly overwriting the register. What is your preference? Are
> > you OK with including OFPACT_REG_MOVE unconditionally?
>
> Yes, it's fine with me.
I've posted patch with a new subject
[PATCH] ofp-actions: Include OFPACT_REG_MOVE in action set
to implement what we just discussed.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
