Actually not :) We dropped dependency on dpdk ptype due to history of issues and lack of mpls ptype and we purely rely on ethertype.
From the metadata only thing we use today is ip4 hdr checksum. > On 5 Jun 2017, at 14:56, Dave Wallace <dwallac...@gmail.com> wrote: > > To be pedantic, the VPP dpdk-input node checks the classification metadata > for each packet which was set by DPDK and decides whether to bypass the > ethernet-input node. > > Thanks, > -daw- > >> On 6/5/2017 3:23 AM, Nagaprabhanjan Bellari wrote: >> DPDK can be thought of as a device driver - there can be multiple device >> drivers - tap interface handler is also, technically, a device driver. So >> are the host-if, ssvm etc. etc. Their job is to collect packets from their >> respective "media" (a physical interface for dpdk, kernel for tap, shared >> memory for ssvm etc.) and hand them off to VPP. >> >> DPDK essentially collects the packets and feeds them to the VPP forwarding >> engine. VPP will then start parsing the packet. It so happens that DPDK does >> some optimization and directly feeds the packet to IP rather than to the >> ethernet node in the graph (because Intel adapters can validate IP checksum >> etc.). Without optimization (for other device drivers) the packets go to >> ethernet input and gets processed from byte 0 of the packet. >> >> Hope this helps. >> >> Thanks, >> -nagp >> >>> On Mon, Jun 5, 2017 at 11:59 AM, Mahesh Ishwar Mathad >>> <mi.mah...@globaledgesoft.com> wrote: >>> Thanks for the great support. >>> >>> The VPP platform grabs all available packets from RX rings to form a >>> vector of packets. These vector of packets who will classify these >>> packets either DPDK or VPP ?. If it is VPP how VPP will classify packet >>> because what I am thinking for every packet VPP is decapsulating to know >>> which packet actually it is, that particular packet is sent to the >>> respected node. By this doing this mechanism VPP is simply wasting >>> machine cycle. If my thinking is worng, please tell me which algorithm >>> is this VPP is following so that i can understand. >>> >>> -- >>> Thanks & Regards, >>> Mahesh Mathad. >>> >>> Disclaimer:- The information contained in this electronic message and any >>> attachments to this message are intended for the exclusive use of the >>> addressee(s) and may contain proprietary, confidential or privileged >>> information. If you are not the intended recipient, you should not >>> disseminate, distribute or copy this e-mail. Please notify >>> the sender immediately and destroy all copies of this message and any >>> attachments. The views expressed in this E-mail message (including the >>> enclosure/(s) or attachment/(s) if any) are those of the individual sender, >>> except where the sender expressly, and with authority, states them to be >>> the views of GlobalEdge. Before opening any mail and attachments please >>> check them for viruses .GlobalEdge does not accept any liability for virus >>> infected mails. >>> >>> _______________________________________________ >>> vpp-dev mailing list >>> vpp-dev@lists.fd.io >>> https://lists.fd.io/mailman/listinfo/vpp-dev >> >> >> >> _______________________________________________ >> vpp-dev mailing list >> vpp-dev@lists.fd.io >> https://lists.fd.io/mailman/listinfo/vpp-dev > > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
