[dpdk-dev] [PATCH] hash: fix memcmp function pointer in multi-process environment

Hi Michael If you agree on the #ifdef protection I explained in my previous mail, I will re-submit the patch with refactoring the the commit log with less than 80 characters per line. Thanks Dhana On Thu, Mar 3, 2016 at 8:00 PM, Dhananjaya Reddy Eadala wrote: > Hi Michael > > Plea

[dpdk-dev] [PATCH] hash: fix memcmp function pointer in multi-process environment

Hi Michael Please see my answers to your comments here. 1. Sure, I will refactor the commit log to restrict not more than 80 characters. 2. Not sure how we can ifdef at the location you mentioned. Can you please elaborate more on this. We already have similar ifdef protection to what you sug

[dpdk-dev] [PATCH] hash: fix memcmp function pointer in multi-process

; > -Original Message- > > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Dhananjaya Reddy > > Eadala > > Sent: Wednesday, March 02, 2016 2:02 PM > > To: Qiu, Michael > > Cc: dev at dpdk.org > > Subject: Re: [dpdk-dev] [PATCH] hash: fix

[dpdk-dev] [PATCH] hash: fix memcmp function pointer in multi-process

Michael Please find the attached is the patch file generated from "git format-patch -1" Thanks Dhana On Tue, Mar 1, 2016 at 9:29 PM, Qiu, Michael wrote: > On 3/2/2016 2:57 AM, Dhananjaya Reddy Eadala wrote: > > Hi > > > > We found a problem in dpdk-2.2 using

[dpdk-dev] [PATCH] hash: fix memcmp function pointer in multi-process

Hi We found a problem in dpdk-2.2 using under multi-process environment. Here is the brief description how we are using the dpdk: We have two processes proc1, proc2 using dpdk. These proc1 and proc2 are two different compiled binaries. proc1 is started as primary process and proc2 as secondary pr