On Mon, Sep 08, 2008, David Hawthorne wrote: > btw, one of the surprising tricks we learned was that the range > start_port end_port specification won't fill up TCAM on the 6500/7600 > IFF your port ranges fall on bit boundaries just like networks do.
I'm sure I've read that documented somewhere. which isn't surprising if "port range" in TCAM is implemented using mask/eval like IP address matching - I guess it'd have to create one mask and multiple match entries to represent your non-contig bit port boundaries. (That may be the motivation behind the earlier TCAM of "limited masks/lots more matches" .. ?) Anyway, too much armchair conjecture from this non-neteng.. back to coding. :) Adrian _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
