Actually, ODP already has this concept. It's called user metadata and was to be a feature of ODP pools (the structures to support this are actually already part of linux-generic). We deferred it from ODP v1.0 for practical reasons, but this is something we should revisit.
Let's put this on the list of architecture things to discuss next week. I'd like to understand the specifics of the OVS need so we can be sure to get the best application match to the final ODP proposal. On Fri, Mar 20, 2015 at 11:43 AM, Zoltan Kiss <[email protected]> wrote: > > > On 20/03/15 16:42, Zoltan Kiss wrote: > >> No, I need to allocate all the packets from the pool and preset some >> fields in the packet metadata area, where OVS store it's ofpbuf >> structure. Setting it after every receive has a perf penalty. See >> "netdev-odp: allocate packet metadata in the same buffer as the packet >> itself" in the previous series. That's where this originally comes from. >> > > Forgot to mention: this is something DPDK has facility for, you can add > initializer functions for the buffer pool create function there. We > discussed with Bill that something like that would be good for ODP. > > > _______________________________________________ > lng-odp mailing list > [email protected] > http://lists.linaro.org/mailman/listinfo/lng-odp >
_______________________________________________ lng-odp mailing list [email protected] http://lists.linaro.org/mailman/listinfo/lng-odp
