Thomas - would you like to explain more on the origins of "rte"? Please note that dpdk API and its public data structures use an rte_ prefix, for example: rte_create_flow(). This is a convenient way to know when we are directly calling/accessing the DPDK library. In parallel we should avoid prefixing rte_ to any OVS owned APIs or structures. In any case "rte" is widely used inside OVS with things related to dpdk.
I have sent v2 which fixes the compilation error (when compiled for kernel only without dpdk) which was caused by an unreferenced call inside dpif-netdev. This call is only relevant to dpdk and is only relevant when configuring "--with-dpdk=". Regards, Ophir > -----Original Message----- > From: [email protected] <ovs-dev- > [email protected]> On Behalf Of Ian Stokes > Sent: Thursday, April 18, 2019 6:59 PM > To: Ben Pfaff <[email protected]>; Aaron Conole <[email protected]> > Cc: [email protected] > Subject: Re: [ovs-dev] [ovs-dev, v1] netdev-rte-offloads: Reassign vport > netdev functions. > > On 4/17/2019 5:34 PM, Ben Pfaff wrote: > > On Wed, Apr 17, 2019 at 11:45:33AM -0400, Aaron Conole wrote: > >> rte comes from dpdk as an acronym for Run Time Environment. Maybe > >> even just dropping the 'rte_' portion? > > > > *That* is what rte stands for? What a ridiculously generic name. > > It's like naming a library Operating System. > > This piqued my interest also, with DPDK in the early days it was targeting > bare > metal comms systems, so the original API was LWRTE (LiteWeight Run Time > Environment) which became RTE as it moved on from bare metal, so it seems > more of a legacy convention. > > Ian > > _______________________________________________ > dev mailing list > [email protected] > https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail. > openvswitch.org%2Fmailman%2Flistinfo%2Fovs- > dev&data=02%7C01%7Cophirmu%40mellanox.com%7C7961fde350f149 > b17ede08d6c416d1f3%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C1%7 > C636911999634142236&sdata=m5LKiyrnAtWO3vpVTyWiQXsnLlhq5ma14 > MydfFiXmfI%3D&reserved=0 _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
