From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id BE6931B142 for ; Thu, 4 Oct 2018 21:16:25 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Oct 2018 12:16:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,341,1534834800"; d="scan'208";a="94697047" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga004.fm.intel.com with ESMTP; 04 Oct 2018 12:16:18 -0700 Received: from fmsmsx151.amr.corp.intel.com ([169.254.7.87]) by FMSMSX106.amr.corp.intel.com ([169.254.5.133]) with mapi id 14.03.0319.002; Thu, 4 Oct 2018 12:16:18 -0700 From: "Wang, Yipeng1" To: Honnappa Nagarahalli , "Van Haaren, Harry" , "Richardson, Bruce" CC: "De Lara Guarch, Pablo" , "dev@dpdk.org" , "Gavin Hu (Arm Technology China)" , "Steve Capper" , Ola Liljedahl , nd , "Gobriel, Sameh" Thread-Topic: [dpdk-dev] [PATCH 3/4] hash: fix rw concurrency while moving keys Thread-Index: AQHUW5X+bax34gG0cU6nYLfhq4Khm6UPSvqg Date: Thu, 4 Oct 2018 19:16:17 +0000 Message-ID: References: <1536253938-192391-1-git-send-email-honnappa.nagarahalli@arm.com> <1536253938-192391-4-git-send-email-honnappa.nagarahalli@arm.com> <20180928082610.GA7592@bricha3-MOBL.ger.corp.intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjE3NmQwN2UtZGI4Zi00ZmFlLWE4MWYtOWI5NWVjMjIxNzRjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiRFlFNWV5aEJFOHlcL1hlZFB2V2E2SmdBXC9kank5ZWJnbXJwYVphS1VaOGNyMzNTMGU3MTBkaFFidXM2Y29sTVJJIn0= x-originating-ip: [10.1.200.106] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 3/4] hash: fix rw concurrency while moving keys X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2018 19:16:26 -0000 >-----Original Message----- >From: Honnappa Nagarahalli [mailto:Honnappa.Nagarahalli@arm.com] >Sent: Wednesday, October 3, 2018 8:54 PM >To: Honnappa Nagarahalli ; Wang, Yipeng1 ; Van Haaren, Harry >; Richardson, Bruce >Cc: De Lara Guarch, Pablo ; dev@dpdk.org; = Gavin Hu (Arm Technology China) >; Steve Capper ; Ola Liljedahl ; nd ; Gobriel, >Sameh >Subject: RE: [dpdk-dev] [PATCH 3/4] hash: fix rw concurrency while moving = keys > >> >> > >-----Original Message----- >> > >From: Van Haaren, Harry >> > >> > > > > /** >> > >> > > > > * Add a key to an existing hash table. >> > >> > > > >@@ -222,7 +222,7 @@ rte_hash_add_key(const struct rte_hash >> > >> > > > >*h, const void >> > >> > > *key); >> > >> > > > > * array of user data. This value is unique for this ke= y. >> > >> > > > > */ >> > >> > > > > int32_t >> > >> > > > >-rte_hash_add_key_with_hash(const struct rte_hash *h, const >> > >> > > > >void *key, >> > >> > > hash_sig_t sig); >> > >> > > > >+rte_hash_add_key_with_hash(struct rte_hash *h, const void >> > >> > > > >+*key, >> > >> > > hash_sig_t sig); >> > >> > > > > >> > >> > > > > / >> > >> > > > >> > >> > > > I think the above changes will break ABI by changing the >> > >> > > > parameter >> > >> type? >> > >> > > Other people may know better on this. >> > >> > > >> > >> > > Just removing a const should not change the ABI, I believe, >> > >> > > since the const is just advisory hint to the compiler. Actual >> > >> > > parameter size and count remains unchanged so I don't believe t= here >> is an issue. >> > >> > > [ABI experts, please correct me if I'm wrong on this] >> > >> > >> > >> > >> > >> > [Certainly no ABI expert, but...] >> > >> > >> > >> > I think this is an API break, not ABI break. >> > >> > >> > >> > Given application code as follows, it will fail to compile - even >> > >> > though >> > >> running >> > >> > the new code as a .so wouldn't cause any issues (AFAIK). >> > >> > >> > >> > void do_hash_stuff(const struct rte_hash *h, ...) { >> > >> > /* parameter passed in is const, but updated function >> > >> > prototype is >> > >> non- >> > >> > const */ >> > >> > rte_hash_add_key_with_hash(h, ...); } >> > >> > >> > >> > This means that we can't recompile apps against latest patch >> > >> > without application code changes, if the app was passing a const >> > >> > rte_hash struct >> > >> as >> > >> > the first parameter. >> > >> > >> > >> Agree. Do we need to do anything for this? >> > > >> > >I think we should try to avoid breaking API wherever possible. >> > >If we must, then I suppose we could follow the ABI process of a >> > >deprecation notice. >> > > >> > >From my reading of the versioning docs, it doesn't document this case= : >> > >https://doc.dpdk.org/guides/contributing/versioning.html >> > > >> > >I don't recall a similar situation in DPDK previously - so I suggest >> > >you ask Tech board for input here. >> > > >> > >Hope that helps! -Harry >> > [Wang, Yipeng] >> > Honnappa, how about use a pointer to the counter in the rte_hash >> > struct instead of the counter? Will this avoid API change? >> I think it defeats the purpose of 'const' parameter to the API and provi= des >> incorrect information to the user. >Yipeng, I think I have misunderstood your comment. I believe you meant; we= could allocate memory to the counter and store the >pointer in the structure. Please correct me if I am wrong. >This could be a solution, though it will be another cache line access. It = might be ok given that it is a single cache line for entire hash >table. [Wang, Yipeng] Yeah that is what I meant. It is an additional memory access= but probably it will be in local cache. Since time is tight, it could be a simple workaround for this version and i= n future you can extend this pointed counter to a counter array as Ola sugg= ested and the Cuckooo switch paper did for scaling issue.=20 > >> IMO, DPDK should have guidelines on how to handle the API compatibility >> breaks. I will send an email to tech board on this. >> We can also solve this by having counters on the bucket. I was planning = to do >> this little bit later. I will look at the effort involved and may be do = it now.