Hello Greg, Thanks for your reply !
Followed your instruction and tried to print the Device name but it prints the Bridge name and Bridge Interface name. I am sharing the two screenshot one is the Log image and another is the ovs-vsctl show output(*netdev type is Internal)*, Please give your suggestion. And I would like you to give you suggestion for the below issue 1. I am planning to extend the queue at egress port of the ovs to 8 queues but really don't have the exact clue where should i change the code , should i explore Linux qdisc like pfifo_fast or something else . Regards Rakesh Kumar On Mon, Aug 27, 2018 at 8:56 PM Gregory Rose <[email protected]> wrote: > > On 8/27/2018 5:09 AM, rakesh kumar wrote: > > Hi Team, > > > > I am was trying to put log in the datapath module in Linux environment to > > trace the flow if we ping one host to another host using ovs switch(using > > mininet emulator).. > > > > Inside *vport.c* file *ovs_vport_send *function is being called and then > > internally it calls *vport->ops->send*() function I am unable to trace > from > > this function , can anyone tell me *where the call will go after calling > > vport->ops->send* function inside* vport.c* file. > > > > > > Please give your valuable suggestions ! > > It will go to the vport driver's registered send function - you can get > the name via the vport > structure's net_device member dev->name. > > - Greg > >
_______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
