[Edited Message Follows]
Thanks Christian and Florin. I am trying without a foreach loop. Things are
looking good so far.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14110): https://lists.fd.io/g/vpp-dev/message/14110
Mute This Topic: https://l
Thanks Christian and Florin. I am trying without a foreach loop. things are
looking good so far.
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#14110): https://lists.fd.io/g/vpp-dev/message/14110
Mute This Topic: https://lists.fd.io/mt/34376308/216
Hi Ranadip,
Yes, the session layer updates all vms when it adds a new arc from
session_queue_node to whatever the transport wants to use for output. I don’t
remember now why we did things that way, but it may be that it’s not needed
anymore.
Florin
> On Oct 2, 2019, at 9:23 PM, Ranadip Das
The session_register_transport() has the foreach code.
1381 /* *INDENT-OFF* */
1382 if (output_node != ~0)
1383 {
1384 foreach_vlib_main (
https://docs.fd.io/vpp/19.08/db/d96/threads_8h.html#a26faa6aef056b1bbb12dc83ce874923c
) (({
1385 next_index = vlib_node_add_next (
https://docs.fd.io/vpp/19
> On Oct 2, 2019, at 6:48 PM, Ranadip Das wrote:
>
> Hello,
>
> I am seeing vlib_node_add_next is getting used in two different ways.
>
> vlib_node_add_next(vm, node_index, next_node_index);
>
> And
>
> foreach_vlib_main (({
> next_index = vlib_node_add_next (this_vlib_main, node_index
Hello,
I am seeing vlib_node_add_next is getting used in two different ways.
vlib_node_add_next(vm, node_index, next_node_index);
And
foreach_vlib_main (({
next_index = vlib_node_add_next (this_vlib_main, node_index, next_node_index);
}));
The first one (without foreach_vlib_main) calls vlib_n
