From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH] lcore: make semantics of lcore role function more intuitive Date: Thu, 26 Apr 2018 08:38:42 -0700 Message-ID: <20180426083842.5fc6c83c@xeon-e3> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, Neil Horman , John McNamara , Marko Kovacevic , Robert Sanford , thomas@monjalon.net, erik.g.carrillo@intel.com, olivier.matz@6wind.com To: Anatoly Burakov Return-path: Received: from mail-pf0-f196.google.com (mail-pf0-f196.google.com [209.85.192.196]) by dpdk.org (Postfix) with ESMTP id B36168BA7 for ; Thu, 26 Apr 2018 17:38:45 +0200 (CEST) Received: by mail-pf0-f196.google.com with SMTP id f15so18703013pfn.0 for ; Thu, 26 Apr 2018 08:38:45 -0700 (PDT) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Thu, 26 Apr 2018 14:42:31 +0100 Anatoly Burakov wrote: > rte_lcore_has_role() returns 0 if role of lcore matches requested > role. The return value of the API is confusing, and this is a known > problem with a deprecation notice announcing the change to more > intuitive semantics: > > Commit 064518f68d48 ("doc: announce EAL API change to lcore role function") > Cc: erik.g.carrillo@intel.com > > Implement changes announced in the deprecation notice, and remove it. > Also, fix usages of this API to reflect the change. Control thread patches > expected new behavior and were broken before, now they are fixed as well. > > Fixes: d651ee4919cd ("eal: set affinity for control threads") > Cc: olivier.matz@6wind.com > > Signed-off-by: Anatoly Burakov It would make more sense if rte_lcore_has_role returned a bool