Re: [RFC] ematch API, u32 ematch, nbyte ematch, basic classifier

On Wed, 2005-01-05 at 11:48, Thomas Graf wrote:

Here's what I mean, it moves the u32 match as-is to an ematch so it
benefits from logic relations, inversion and can be used from other
classifiers as well. All we have to do is set info->ptr and
info->nexthdr to ptr respetively off2 before we evaluate the ematch
tree. The pkt_info struct is then passed to tcf_em_tree_match and
made available to every ematch.

Thoughts?

I think this is fine; getting into complicated-land with off2 etc but
fine and does not preclude (and is lower importance in my opinion) than
having u32 do its own magic. 
Note again Thomas: I do realize its more work to do the ematch/match
thing ;->

cheers,
jamal