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 B2C8945B57; Thu, 17 Oct 2024 07:40:55 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2E8A24021F; Thu, 17 Oct 2024 07:40:55 +0200 (CEST) Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3]) by mails.dpdk.org (Postfix) with ESMTP id D3BC140144 for ; Thu, 17 Oct 2024 07:40:53 +0200 (CEST) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 63C6B1BB2C for ; Thu, 17 Oct 2024 07:40:53 +0200 (CEST) Received: by mail.lysator.liu.se (Postfix, from userid 1004) id 55A3B1BC0E; Thu, 17 Oct 2024 07:40:53 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on hermod.lysator.liu.se X-Spam-Level: X-Spam-Status: No, score=-1.2 required=5.0 tests=ALL_TRUSTED,AWL, T_SCC_BODY_TEXT_LINE autolearn=disabled version=4.0.0 X-Spam-Score: -1.2 Received: from [192.168.1.85] (h-62-63-215-114.A163.priv.bahnhof.se [62.63.215.114]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id 3994B1BBB7; Thu, 17 Oct 2024 07:40:51 +0200 (CEST) Message-ID: <5e9cc9d9-4605-4e06-99d3-0f2aeac2f957@lysator.liu.se> Date: Thu, 17 Oct 2024 07:40:50 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v14 0/7] Lcore variables To: Stephen Hemminger , =?UTF-8?Q?Mattias_R=C3=B6nnblom?= Cc: dev@dpdk.org, =?UTF-8?Q?Morten_Br=C3=B8rup?= , Konstantin Ananyev , David Marchand , Jerin Jacob , Luka Jankovic References: <20241015093344.824073-2-mattias.ronnblom@ericsson.com> <20241016131916.827788-1-mattias.ronnblom@ericsson.com> <20241016075810.7f953ea7@hermes.local> Content-Language: en-US From: =?UTF-8?Q?Mattias_R=C3=B6nnblom?= In-Reply-To: <20241016075810.7f953ea7@hermes.local> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP 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 2024-10-16 16:58, Stephen Hemminger wrote: > On Wed, 16 Oct 2024 15:19:09 +0200 > Mattias Rönnblom wrote: > >> This patch set introduces a new API for static >> per-lcore id data allocation. >> >> Please refer to the API documentation for both a >> rationale for this new API, and a comparison to the alternatives >> available. >> >> The question on how to best allocate static per-lcore memory has been >> up several times on the dev mailing list, for example in the thread on >> "random: use per lcore state" RFC by Stephen Hemminger. >> >> Lcore variables are surely not the answer to all your per-lcore-data >> needs, since it only allows for more-or-less static allocation. In the >> author's opinion, it does however provide a reasonably simple and >> clean and seemingly very much performant solution to a real problem. >> >> Mattias Rönnblom (7): >> eal: add static per-lcore memory allocation facility >> eal: add lcore variable functional tests >> eal: add lcore variable performance test >> random: keep PRNG state in lcore variable >> power: keep per-lcore state in lcore variable >> service: keep per-lcore state in lcore variable >> eal: keep per-lcore power intrinsics state in lcore variable > > Still too wordy, would you mind if I have a try and summarizing and > running the text through an editor tool? I think you need to be a little more wordy here. What text? The cover text? That won't survive anyway.