Re: [lng-odp] [API-NEXT PATCHv2 00/16] using _ishm as north API mem allocator

2016-10-19 Thread Mike Holmes
After todays call with Petris patches posted that also break IPC we came up with a plan. 1. sync api-next / master and make a point release to clear the air 2. merge into api next Christophes and Petris patches that break IPC 3. Maxim will fix IPC 4. make a new point release On 18 October 2016 at

Re: [lng-odp] [API-NEXT PATCHv2 00/16] using _ishm as north API mem allocator

2016-10-18 Thread Bill Fischofer
This looks good. Minor doc corrections/suggestions noted in part 16. Given that this breaks the current IPC implementation is should not be merged until Maxim has a sympathetic IPC update to link to these changes. For this series: Reviewed-and-tested-by: Bill Fischofer On Tue, Oct 18, 2016 at 6

[lng-odp] [API-NEXT PATCHv2 00/16] using _ishm as north API mem allocator

2016-10-18 Thread Christophe Milard
since v1: -flag _ODP_SHM_PROC_NOCREAT and _ODP_SHM_O_EXCL get new values (but remain useless: Should be removed when IPC is updated) (Maxim) -In get_ishm_flags(), odp_shm_capability() local variable flgs renamed (for be better distinction from other "flags" variable. (Maxim) -Added doc updates w