Artifacts from https://github.com/floodlight/loxigen/compare/3c2fb9914cc8e40feb73b3acf2dff8d4bb46b099...4c9d1ec52942d8d11847d0374903b221b41d5646

Loxigen Head commit floodlight/loxigen@4c9d1ec52942d8d11847d0374903b221b41d5646
commit 4c9d1ec52942d8d11847d0374903b221b41d5646
Merge: 3c2fb99 68798a5
Author: abat <abat@bigswitch.com>
Date:   Wed Apr 16 15:24:29 2014 -0700

    Merge into master from pull request #239:
    loci: only mask partially wildcarded fields (https://github.com/floodlight/loxigen/pull/239)

commit 68798a590dfdde98fda2f2c8a83e860156b74dac
Author: Rich Lane <rlane@bigswitch.com>
Date:   Wed Apr 16 14:57:52 2014 -0700

    loci: cleanup of_memmask and remove of_match_values_mask

commit 054a818b70e7b62356b07e466668c390d6f29216
Author: Rich Lane <rlane@bigswitch.com>
Date:   Wed Apr 16 14:42:41 2014 -0700

    loci: use of_memmask for OF 1.1

commit d5f234506eaeaeddd3209f6e0eb4167a1817b355
Author: Rich Lane <rlane@bigswitch.com>
Date:   Thu Apr 3 01:16:37 2014 -0700

    loci: only mask partially wildcarded fields

    The of_match_values_mask function was consuming about 7% CPU time in my
    benchmarks. For realistic flows most of the work it did was pointless, because
    most fields are fully wildcarded and most of the rest are not wildcarded. Only
    in the uncommon case of partially wildcarded fields does this function do
    anything.

    Fixed by calling a new of_memmask function only when parsing a masked OXM.