Re: [dpdk-dev] [PATCH v3 5/5] eal: don't hardcode socket filter value in IPC

2018-02-28 Thread Tan, Jianfeng
On 2/28/2018 6:21 PM, Burakov, Anatoly wrote: On 28-Feb-18 1:52 AM, Tan, Jianfeng wrote: Hi Anatoly, -Original Message- From: Burakov, Anatoly Sent: Tuesday, February 27, 2018 10:36 PM To: dev@dpdk.org Cc: Tan, Jianfeng Subject: [PATCH v3 5/5] eal: don't hardcode socket filter value

Re: [dpdk-dev] [PATCH v3 5/5] eal: don't hardcode socket filter value in IPC

2018-02-28 Thread Burakov, Anatoly
On 28-Feb-18 1:52 AM, Tan, Jianfeng wrote: Hi Anatoly, -Original Message- From: Burakov, Anatoly Sent: Tuesday, February 27, 2018 10:36 PM To: dev@dpdk.org Cc: Tan, Jianfeng Subject: [PATCH v3 5/5] eal: don't hardcode socket filter value in IPC Currently, filter value is hardcoded and

Re: [dpdk-dev] [PATCH v3 5/5] eal: don't hardcode socket filter value in IPC

2018-02-27 Thread Tan, Jianfeng
Hi Anatoly, > -Original Message- > From: Burakov, Anatoly > Sent: Tuesday, February 27, 2018 10:36 PM > To: dev@dpdk.org > Cc: Tan, Jianfeng > Subject: [PATCH v3 5/5] eal: don't hardcode socket filter value in IPC > > Currently, filter value is hardcoded and disconnected from actual > val

[dpdk-dev] [PATCH v3 5/5] eal: don't hardcode socket filter value in IPC

2018-02-27 Thread Anatoly Burakov
Currently, filter value is hardcoded and disconnected from actual value returned by eal_mp_socket_path(). Fix this to generate filter value by deriving it from eal_mp_socket_path() instead. Signed-off-by: Anatoly Burakov --- Notes: v3: no changes v2: no changes lib/librte_eal/comm