From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH] rte_reciprocal: make arg to rte_reciprocal_divide_u64 const Date: Wed, 27 Mar 2019 12:14:44 +0100 Message-ID: <4147107.f6clCcuQYr@xps> References: <20190321195910.11140-1-stephen@networkplumber.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, maxime.coquelin@redhat.com To: Stephen Hemminger Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 70A7D5B26 for ; Wed, 27 Mar 2019 12:14:47 +0100 (CET) In-Reply-To: <20190321195910.11140-1-stephen@networkplumber.org> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 21/03/2019 20:59, Stephen Hemminger: > The divisor is not modified here. Doesn't really matter for optimizaton > since the function is inline already; but helps with expressing > intent. > > Signed-off-by: Stephen Hemminger > --- > static __rte_always_inline uint64_t > -rte_reciprocal_divide_u64(uint64_t a, struct rte_reciprocal_u64 *R) > +rte_reciprocal_divide_u64(uint64_t a, const struct rte_reciprocal_u64 *R) Why not doing the same change for rte_reciprocal_divide()? Should we advertise such API change?