[ovs-discuss] mf_value and mf_subvalue size restrictions

[Ben Pfaff]

On Thu, Nov 06, 2014 at 03:02:45PM -0800, Jesse Gross wrote:
> On Thu, Nov 6, 2014 at 2:49 PM, Ben Pfaff <blp at nicira.com> wrote:
> > Have you considered allowing database configuration to specify what kind
> > of attributes are expected and how to parse them?  The configuration
> > could be P4-based, for example.
> 
> This is possible but it seems kind of ugly and complicated so I hope
> to not have to go down this path. I think there is a simpler variant,
> which is to just have a mapping table of Geneve IDs to a pool of OXMs.
> That's all that is really needed since the action to be taken is just
> matching against the payload so there isn't much parsing. But I still
> would like it avoid this if possible.

I guess I see some form of more configurable header parsing as
inevitable, which makes me eager to try out some kind of prototype.  A
mapping table would be a nice simple place to start.