Thanks Dave, That hints what must be at the 0th index in .next_nodes of a node.
Regards Dharmaray From: Dave Barach (dbarach) [mailto:[email protected]] Sent: Tuesday, June 20, 2017 6:41 PM To: Dharmaray Kundargi <[email protected]>; [email protected] Subject: RE: Default next node for a node. node->cached_next_index will be zero at the beginning of time. Depending on the particulars involved, that might even be correct. If not, the enqueue_x1/enqueue_x2 macros will fix the erroneous speculative enqueues. vlib_put_next_frame(...) maintains node->cached_next_index... Thanks... Dave From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dharmaray Kundargi Sent: Tuesday, June 20, 2017 8:03 AM To: [email protected]<mailto:[email protected]> Subject: [vpp-dev] Default next node for a node. Hi, Was wondering how the speculated next node is decided for first ever packet to a node? In code for every graph node we see the code "next_index = node->cached_next_index;". But where is this node->cached_next_index initialized before the node processes the first ever packet ? Or does it mean it does not matter whatever value this node->cached_next_index is initialized, first time when we try to enqueue the packet node->cached_next_index is initialized based on the actual next0 and next1 ? Regards Dharmaray ________________________________ Please Note: My email address is changing. Starting May 1st 2017 my email will solely be my Mavenir email [email protected]<mailto:[email protected]>. All other prior email accounts will become inactive. To ensure continuity, please send all emails to my Mavenir email ID which is currently active and available for use. This e-mail message may contain confidential or proprietary information of Mavenir Systems, Inc. or its affiliates and is intended solely for the use of the intended recipient(s). If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies in your control and contact us by e-mailing to [email protected]<mailto:[email protected]>. Thank You. This message contains the views of its author and may not necessarily reflect the views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor email messages, but make no representation that such messages are authorized, secure, uncompromised, or free from computer viruses, malware, or other defects. ________________________________ Please Note: My email address is changing. Starting May 1st 2017 my email will solely be my Mavenir email [email protected]. All other prior email accounts will become inactive. To ensure continuity, please send all emails to my Mavenir email ID which is currently active and available for use. This e-mail message may contain confidential or proprietary information of Mavenir Systems, Inc. or its affiliates and is intended solely for the use of the intended recipient(s). If you are not the intended recipient of this message, you are hereby notified that any review, use or distribution of this information is absolutely prohibited and we request that you delete all copies in your control and contact us by e-mailing to [email protected]. Thank You. This message contains the views of its author and may not necessarily reflect the views of Mavenir Systems, Inc. or its affiliates, who employ systems to monitor email messages, but make no representation that such messages are authorized, secure, uncompromised, or free from computer viruses, malware, or other defects.
_______________________________________________ vpp-dev mailing list [email protected] https://lists.fd.io/mailman/listinfo/vpp-dev
