I had looked at some examples some time back. The feeling I got is that, they need to be simple and showcase the functionality of that application. For ex: L2 FWD application in the file odp_l2fwd.c, showcases a lot of functionality, various mode of pkt I/O and different sched types of queues. It also has elaborate functionality to bind the workers to interfaces/queues. If someone is looking at the examples, they are probably new to ODP and do not need this level of details. I would say, keep it simple (similar to L2 FWD simple example).
It can be complicated for the test directory. On 9 December 2016 at 11:16, Mike Holmes <mike.hol...@linaro.org> wrote: > One further thought is that if it in some way benchmarks anything it is > perhaps a candidate for the test performance directory instead. > > On 9 December 2016 at 09:47, Bill Fischofer <bill.fischo...@linaro.org> > wrote: > >> This sounds like an excellent example. The goal of ODP examples is to >> illustrate programming techniques and API usage that may be of >> interest to others in either evaluating ODP and/or writing their own >> applications with it. As such, examples are expected to be reasonably >> succinct and focused, but there is no specific size or complexity >> requirement. >> >> On Fri, Dec 9, 2016 at 8:12 AM, Joe Savage <joe.sav...@arm.com> wrote: >> > Hey, >> > >> > I've been working on an implementation of IPv4 fragmentation and >> > reassembly using ODP, and was wondering whether it might be useful to >> > contribute this to the "example" directory. >> > >> > What exactly are you looking for in ODP examples, and how might I go >> > about preparing this project (or, indeed, some smaller subset of this >> > project) for contribution? >> > >> > Thanks, >> > >> > Joe >> > >> > > > > -- > Mike Holmes > Program Manager - Linaro Networking Group > Linaro.org <http://www.linaro.org/> *│ *Open source software for ARM SoCs > "Work should be fun and collaborative, the rest follows"
