On Fri, Sep 25, 2020 at 4:35 PM hemant via lists.fd.io <hemant= mnkcg....@lists.fd.io> wrote:
> In the classify API mentioned in the subject of this email, I could use an > example with tables to understand table_index, next_table_index, and > miss_next_index. I know VPP maintains an index for a table. > > > > Say, the tables are invoked in this order for this example: > > > > Ethernet-input, ip4-iput, pkt_filter4 (my new table), rewrite > > > > If table_index is that of pkt_filter4, I suppose, next_table_index is > rewrite? I am not sure what is miss_next_index which is invoked if > pkt_filter4 incurs a miss. > Hemant. The items you listed above are graph nodes. They are not classifier table indices. I will grant you these are confusing names, everything is an index into some table. The classifier tables are chained via the next_table_index field. After a miss searching in one table, the search continues in the next_table_index classifier table if it is available. If the next_table_index does not exist, the packet is handed off to the graph node given as miss_next_index. If a lookup within a table hits, the "next_index" is the graph node that will receive the packet. Fair warning: I _think_ this is how it works. I've only just read through this code recently myself. :-) HTH, jdl
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17580): https://lists.fd.io/g/vpp-dev/message/17580 Mute This Topic: https://lists.fd.io/mt/77126788/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
