> 21/04/2019 11:11, Ophir Munk: >> Thomas - would you like to explain more on the origins of "rte"? > > Ian explained (below) the origin quite clearly. > It has been decided in the early days by Intel. > >> From: Ian Stokes >> > 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. > > Yes I agree that it's ridiculous :)
The best header is "rte_eal.h". It looks like DPDK tries to abstract from itself. > > I already proposed to replace rte_ with dpdk_ prefix > but the vast majority was against a big replacement. > Would you support such a change? I'm not contributing much to dpdk these days, but I'd support such a change. This would be a big step toward apps that tries to work with DPDK as a library and not as a run-time environment. And, probably, right now is the last chance for DPDK do make such a huge API break. There was way too much discussions about API stability and I'm afraid that DPDK will petrify soon without ability to change anything. > >> > 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. > _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
