Re: [dpdk-dev] [PATCH] memzone: Check socket_id value when creating memzone.

2017-06-05 Thread Thomas Monjalon
12/05/2017 10:42, Bruce Richardson: > On Thu, May 11, 2017 at 11:03:43PM -0700, Tonghao Zhang wrote: > > If the socket_id is invalid (e.g. -2, -3), the > > memzone_reserve_aligned_thread_unsafe should return the > > EINVAL and not ENOMEM. To avoid it, we should check the > > socket_id before callin

Re: [dpdk-dev] [PATCH] memzone: Check socket_id value when creating memzone.

2017-05-31 Thread nickcooper-zhangtonghao
If that patch is ok, will we apply it to master? Thanks. Nick > On May 12, 2017, at 4:42 PM, Bruce Richardson > wrote: > > On Thu, May 11, 2017 at 11:03:43PM -0700, Tonghao Zhang wrote: >> If the socket_id is invalid (e.g. -2, -3), the >> memzone_reserve_aligned_thread_unsafe should return the

Re: [dpdk-dev] [PATCH] memzone: Check socket_id value when creating memzone.

2017-05-16 Thread nickcooper-zhangtonghao
> On May 12, 2017, at 4:42 PM, Bruce Richardson > wrote: > > On Thu, May 11, 2017 at 11:03:43PM -0700, Tonghao Zhang wrote: >> If the socket_id is invalid (e.g. -2, -3), the >> memzone_reserve_aligned_thread_unsafe should return the >> EINVAL and not ENOMEM. To avoid it, we should check the >>

Re: [dpdk-dev] [PATCH] memzone: Check socket_id value when creating memzone.

2017-05-12 Thread Bruce Richardson
On Thu, May 11, 2017 at 11:03:43PM -0700, Tonghao Zhang wrote: > If the socket_id is invalid (e.g. -2, -3), the > memzone_reserve_aligned_thread_unsafe should return the > EINVAL and not ENOMEM. To avoid it, we should check the > socket_id before calling malloc_heap_alloc. > > Signed-off-by: Tongh