Does anyone have an input on this ? Thanks, Monica
-----Original Message----- From: Rajasekaran, Monica Sent: Thursday, March 10, 2016 2:55 PM To: 'dsa...@cs.technion.ac.il'; discuss@openvswitch.org Subject: RE: [ovs-discuss] Phy port- vport Thanks for pointing that out David. One more question: When we add-port using vsctl, that gets added to the bridge and lets us map to a physical port right. So, where does vport come in here ? I mean, how does it map with the physical port? I see from the code that vports are used to receive packets coming to the switch (ovs_vport_receive) and to send (ovs_vport_send). Thanks, Monica -----Original Message----- From: discuss [mailto:discuss-boun...@openvswitch.org] On Behalf Of dsa...@cs.technion.ac.il Sent: Wednesday, March 09, 2016 8:05 PM To: discuss@openvswitch.org Subject: Re: [ovs-discuss] Queuing a packet to user space Hi Monica, The messaging mechanism that OVS is using is provided by the operating system, OVS doesn't implement it, it just uses and invokes it. cheers, David. > Hi all, > > Once call in the data path hits queue_userspace_packet(), how is the > packet received by user space ? > > I understand that recv_upcalls-->dpif_recv() and handle_upcalls() will > take care of upcall processing. > > But how are queue_userspace_packet() in the data path and > recv_upcalls() in the user space connected? I can't seem to find the link. > > Thanks, > Monica > > _______________________________________________ > discuss mailing list > discuss@openvswitch.org > http://openvswitch.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
