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 D68CC44106; Wed, 29 May 2024 23:55:23 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C9273402B0; Wed, 29 May 2024 23:55:23 +0200 (CEST) Received: from mail-pf1-f169.google.com (mail-pf1-f169.google.com [209.85.210.169]) by mails.dpdk.org (Postfix) with ESMTP id 0EC1A40273 for ; Wed, 29 May 2024 23:55:23 +0200 (CEST) Received: by mail-pf1-f169.google.com with SMTP id d2e1a72fcca58-70231566377so81347b3a.0 for ; Wed, 29 May 2024 14:55:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1717019722; x=1717624522; darn=dpdk.org; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=Jn5l1X7W6x16WUGDM5VLG79KcjzUeJ2uCo3f/iThAio=; b=Sx40pMUzHxTmaXrelfV9eXPbYH+9xtVhib3knCv9tSj3HZO+tkvwx8PaDkZBgGKYYo Elck1PmTn2cbIbK0Wv3FA6OZknA2Pnf3gDL32AwWVKWkiRK4BtljRGgaGSL2NmevEzp6 2C1LY28CRuRw7bwpJP2si0ndEYX4F//hdrieHovQo4MObhILGhL5lRcdB9y9crBvKD01 Pdnhb8MLm7PF9CWwY6X35EF3pp4OVhjqXklR/1aBNtRa9ZrO9kZL3ePb19yNH1SFUKXo 54PtGlhW619hYh3jrDHs5DZJmF2So8unQgcjzD0jU7eRKZ7+kThy2BD66U/yyj2H4Fhp LeGQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717019722; x=1717624522; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=Jn5l1X7W6x16WUGDM5VLG79KcjzUeJ2uCo3f/iThAio=; b=bolkrzksB/nbM4lKdLxO3gDic0cWO9hMZ92AkC4rTxQvTx8tAwfMN7MrnWdepbtaay KK41DdNhclZws0R5KuqbGl2Ie554EIBedRfeJSSivDJ486olv33wSUJ+Qf8yqzCiBXOx k6jarY0xk+Ok+l98o46KgyshWSDJG/y58ya6HHAnHxnwDXwXfDNso3Y69slq+HOqe+tn Eq0xX7WBhYEsANsffJpLWPVwpNsfaZfnmtAg4ZGR3qYS2f946TFQ+zECpSyv1fPNxbaa YDWvH41B+W6TUrWEm0Ivuq8dwTYhexbr0KJeeAYUUwJ60gsyE0QX2/drBhf3QeNeYkZD tHLA== X-Forwarded-Encrypted: i=1; AJvYcCV49HkkmGI1h0B4n2z9nindMwgZrWQVwT0sCnfsGGA9m9w+1zMwhVY4RIi7xa6ChU5pYCYZPrvBX5YjF1w= X-Gm-Message-State: AOJu0YwvXHgDOERkCqnpJrbfK20DV3C1Ypr8s2RMolCvAkFikZuI1+WF cE57gtBrorqEvMs055epKS+cP+OoGas6nWqVR/75GRiyamrnlTp15TaxyQO6jCw= X-Google-Smtp-Source: AGHT+IED199G8x6c/jXReNUrGCU7staS449QkDO+gEebKUMeZ0rIvUM+6z/E1lHynmCjfbiJ0/V8vA== X-Received: by 2002:a05:6a00:2a0b:b0:6ed:434f:e73a with SMTP id d2e1a72fcca58-702311e374amr272589b3a.30.1717019722150; Wed, 29 May 2024 14:55:22 -0700 (PDT) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7022e9467eesm298843b3a.1.2024.05.29.14.55.21 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 May 2024 14:55:21 -0700 (PDT) Date: Wed, 29 May 2024 14:55:20 -0700 From: Stephen Hemminger To: Mattias =?UTF-8?B?UsO2bm5ibG9t?= Cc: Mattias =?UTF-8?B?UsO2bm5ibG9t?= , dev@dpdk.org, Morten =?UTF-8?B?QnLDuHJ1cA==?= Subject: Re: [RFC v2] eal: provide option to use compiler memcpy instead of RTE Message-ID: <20240529145520.61bc6615@hermes.local> In-Reply-To: <8d51d44d-06b9-4c62-be51-35e90936d2f4@lysator.liu.se> References: <20240527111151.188607-1-mattias.ronnblom@ericsson.com> <20240528074354.190779-1-mattias.ronnblom@ericsson.com> <738e376c-c5b6-44dc-ad51-00f40d2ea6b5@lysator.liu.se> <20240528075936.2110c31c@hermes.local> <8d51d44d-06b9-4c62-be51-35e90936d2f4@lysator.liu.se> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 On Tue, 28 May 2024 18:03:27 +0200 Mattias R=C3=B6nnblom wrote: > > Lets go farther. > >=20 > > 1. Announce that rte_memcpy will be marked deprecated in 24.11 release > >=20 > > 2. In 24.11 do a global replace of rte_memcpy on the tree. > > And mark rte_memcpy as deprecated. > >=20 > > 3. In 25.11 it can go away. =20 >=20 > If/when rte_memcpy.h is just a tiny memcpy() wrapper, the maintenance=20 > burden is pretty much eliminated. >=20 > Keeping it around will allow for older applications to compile against=20 > newer DPDK version. >=20 > You can always discourage its use in the API documentation. >=20 > Also, hopefully, some day, we will have a non-temporal memcpy(), and=20 > those functions needs a home. I was thinking a wrapper but have it marked __rte_deprecated so that warnings result and people are motivated to fix.