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 89B4945B26; Sun, 13 Oct 2024 09:04:08 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6C2E8402C4; Sun, 13 Oct 2024 09:04:08 +0200 (CEST) Received: from mail.lysator.liu.se (mail.lysator.liu.se [130.236.254.3]) by mails.dpdk.org (Postfix) with ESMTP id 7C01340151 for ; Sun, 13 Oct 2024 09:04:06 +0200 (CEST) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 3ABA0AA1D for ; Sun, 13 Oct 2024 09:04:06 +0200 (CEST) Received: by mail.lysator.liu.se (Postfix, from userid 1004) id 1D778A959; Sun, 13 Oct 2024 09:04:06 +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 015BBA957; Sun, 13 Oct 2024 09:04:03 +0200 (CEST) Message-ID: Date: Sun, 13 Oct 2024 09:04:03 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v8 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: <20240918082614.725220-2-mattias.ronnblom@ericsson.com> <20241010141349.813088-1-mattias.ronnblom@ericsson.com> <20241011072326.4a2ec420@hermes.local> Content-Language: en-US From: =?UTF-8?Q?Mattias_R=C3=B6nnblom?= In-Reply-To: <20241011072326.4a2ec420@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-11 16:23, Stephen Hemminger wrote: > On Thu, 10 Oct 2024 16:13:42 +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 adoption of this API would affect many different DPDK modules, but >> the author updated only a few, mostly to serve as examples in this >> RFC, and to iron out some, but surely not all, wrinkles in the API. >> >> 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. > > There should be a mention about whether this storage can be > shared with other threads and processes. Is it like huge page > memory or stack or heap? Sure. I'll mention the memory is not in huge pages in the API docs.