From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6ACA44401D; Mon, 13 May 2024 21:36:45 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CDCA5402F0; Mon, 13 May 2024 21:36:44 +0200 (CEST) Received: from dkmailrelay1.smartsharesystems.com (smartserver.smartsharesystems.com [77.243.40.215]) by mails.dpdk.org (Postfix) with ESMTP id F2C63402CD for ; Mon, 13 May 2024 21:36:42 +0200 (CEST) Received: from smartserver.smartsharesystems.com (smartserver.smartsharesys.local [192.168.4.10]) by dkmailrelay1.smartsharesystems.com (Postfix) with ESMTP id C932E2276B; Mon, 13 May 2024 21:36:42 +0200 (CEST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [RFC v2 1/7] eal: generic 64 bit counter X-MimeOLE: Produced By Microsoft Exchange V6.5 Date: Mon, 13 May 2024 21:36:39 +0200 Message-ID: <98CBD80474FA8B44BF855DF32C47DC35E9F44A@smartserver.smartshare.dk> In-Reply-To: <20240513185448.120356-2-stephen@networkplumber.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [RFC v2 1/7] eal: generic 64 bit counter Thread-Index: AdqlZxSnIdddpEG6TYiZIapsPlhfGAAAzctQ References: <20240510050507.14381-1-stephen@networkplumber.org> <20240513185448.120356-1-stephen@networkplumber.org> <20240513185448.120356-2-stephen@networkplumber.org> From: =?iso-8859-1?Q?Morten_Br=F8rup?= To: "Stephen Hemminger" , X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org > From: Stephen Hemminger [mailto:stephen@networkplumber.org] > Sent: Monday, 13 May 2024 20.52 >=20 > This header implements 64 bit counters that are NOT atomic > but are safe against load/store splits on 32 bit platforms. >=20 > Signed-off-by: Stephen Hemminger > --- As an initial reaction I would have preferred get() instead of fetch(); = get() being more common in DPDK function naming. However, atomic functions use the name fetch(), not get(), and these are = functions are slightly related to atomic functions. So, after further consideration, it seems fetch() is the better choice. Acked-by: Morten Br=F8rup PS: Although I'm usually strongly opposed to EAL bloat... As long as the EAL = also serves as a the library for simple utility functions, this belongs = in the EAL. Specific optimizations for various 32 bit architectures may be added = later.