Re: [lng-odp] Move Typedefs to a new Header File

2014-11-01 Thread Bala Manoharan
Hi, In the Current ODP design, we are having the typedef for different handles defined in the same header file. This causes a circular dependency between odp_buffer.h and odp_buffer_pool.h file as the buffer API uses pool handle and pool API uses buffer Handle. We would like to avoid this

Re: [lng-odp] Move Typedefs to a new Header File

2014-11-01 Thread Bill Fischofer
In the case of odp_buffer.h and odp_buffer_pool.h I'm not sure why it wouldn't make sense to combine these into one file since they are so closely related. We have APIs in odp_buffer.h that take odp_buffer_pool_t arguments (e.g., odp_buffer_copy) and return odp_buffer_pool_t results

Re: [lng-odp] Move Typedefs to a new Header File

2014-11-01 Thread Bill Fischofer
BTW, Bala, In looking at the implementation of these routines I've put the bulk of the info from the design doc into the .h file itself and it seems to be formatting well. To avoid duplication of effort, I suggest you focus on the classification implementation and let's sync up next week on

Re: [lng-odp] Move Typedefs to a new Header File

2014-10-31 Thread Bill Fischofer
Adding the ODP mailing list since this should be a topic of general interest. Now that we have separate repositories for each implementation what we'd ideally like is the following. - The API definitions are in .h files in odp.git. These are the function prototypes for all of the public