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 D35B142553; Sat, 9 Sep 2023 13:32:14 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 61AA54029E; Sat, 9 Sep 2023 13:32:14 +0200 (CEST) Received: from mail-pl1-f180.google.com (mail-pl1-f180.google.com [209.85.214.180]) by mails.dpdk.org (Postfix) with ESMTP id 6C19940295 for ; Sat, 9 Sep 2023 13:32:12 +0200 (CEST) Received: by mail-pl1-f180.google.com with SMTP id d9443c01a7336-1c336f3f449so25048735ad.3 for ; Sat, 09 Sep 2023 04:32:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1694259131; x=1694863931; 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=uO0uWnwL8D7dutLdukN9NvCOcpgHoD2yg5hk5VmN1Ow=; b=AU1+47GKh+trxvOt1nEBUgWP7W+hpb6ZH5WCaYFYSRZLhDioubMO3WeUhG5Pok78BM khL0dHlk9G4oblXjJnq8A+0gBpiihaVblPJODx7FTD6ii0yiSNqJQ3G5fjpJSBEvEEk7 PXIcwdnAnOth6L/ejh77OxETEotbdj3kF7JFrNLhfeXvfdQxiCpxOGWnCkizIQ+CCta9 nzPo4BDqafJzF9dmfnEYB4ejTY9E/0YPmMA9llKHRjGtF0TcI0tmPP2Ywa3vZCyyAQvz Ez9qIFD1GbqLjrChALbxrj5eaE1PEmZ8Qd/mKRhsERWIiyAmBPErRh2fri/RvQNuW2yr w2aw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1694259131; x=1694863931; 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=uO0uWnwL8D7dutLdukN9NvCOcpgHoD2yg5hk5VmN1Ow=; b=td10CHTN89eQ8yNyWiinYI/eJwSxITUI2HfO+PuxDwDD9UBIXBQrR3IJaQJ8N+xfYc 0k0yEX5BweLXusSYzAHbaMJ5+Yq1Rm5J4OIM/M2QQv1B6dgzGpAUMYf+5JoCe4NpyEd8 xkzuWQpYruWkOk/d614Fk6CXoTd8w1sb1NdZSWV0DL0RlNgcC+ZfI8Ff7qNWX+jBRfu3 KxStQpafWgM7g1rTI9Fci2h4zv6PksTRAzfEXPSwATScAtHfFMtaUdOjdaNo8KU6jfbs Y9Jq1G3FVal9cd9BBG0LLyi8kRKrcyoKzptTubBNs918+JhbqQ+c4vQfH6r+ncRPmJwF 9WKA== X-Gm-Message-State: AOJu0YzWIYGw6KLSolgveWTSu7h+U2AiGWkcjIJSBdtTh/uMwEGvvyZF voDuqWK7F758NPltCyWD9/4rag== X-Google-Smtp-Source: AGHT+IFBaoFai5iFahdsVD2uPfqNC0OzJjME9I4lijbh6pZavFN/ZdYRc/JYiyqBCCMaMSgcX2b0wA== X-Received: by 2002:a17:903:181:b0:1bd:aeb3:9504 with SMTP id z1-20020a170903018100b001bdaeb39504mr5352802plg.15.1694259131357; Sat, 09 Sep 2023 04:32:11 -0700 (PDT) Received: from hermes.local (204-195-112-131.wavecable.com. [204.195.112.131]) by smtp.gmail.com with ESMTPSA id j16-20020a170902759000b001b9f032bb3dsm3083660pll.3.2023.09.09.04.32.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 09 Sep 2023 04:32:11 -0700 (PDT) Date: Sat, 9 Sep 2023 04:32:09 -0700 From: Stephen Hemminger To: Mattias =?UTF-8?B?UsO2bm5ibG9t?= Cc: Konstantin Ananyev , dev@dpdk.org, Mattias =?UTF-8?B?UsO2bm5ibG9t?= , Morten =?UTF-8?B?QnLDuHJ1cA==?= Subject: Re: [RFC] random: use per lcore state Message-ID: <20230909043209.47866f0b@hermes.local> In-Reply-To: <4d00a500-a054-b11b-6135-49e4ef7965f2@lysator.liu.se> References: <20230906172013.169846-1-stephen@networkplumber.org> <741c94a4-65f9-c044-b3fc-3b8c28922d48@yandex.ru> <4d00a500-a054-b11b-6135-49e4ef7965f2@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 Sat, 9 Sep 2023 08:45:17 +0200 Mattias R=C3=B6nnblom wrote: > > Hmm.. correct me if I am wrong, but with current implementation, > > rand state is also in non-huge memory: > > static struct rte_rand_state rand_states[RTE_MAX_LCORE + 1]; > > =20 >=20 > Yes. The current pattern is certainly not perfect. There is no good reason to put it in hugepage memory. In fact, hugepage memory is a limited resource and you do want different rand_states for primary and secondary processes.