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 E251746269 for ; Wed, 19 Feb 2025 16:03:25 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6DEC740EF0; Wed, 19 Feb 2025 16:03:25 +0100 (CET) Received: from mail-pj1-f45.google.com (mail-pj1-f45.google.com [209.85.216.45]) by mails.dpdk.org (Postfix) with ESMTP id CB3C740E6E for ; Wed, 19 Feb 2025 16:03:23 +0100 (CET) Received: by mail-pj1-f45.google.com with SMTP id 98e67ed59e1d1-2f9d3d0f55dso9834907a91.1 for ; Wed, 19 Feb 2025 07:03:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20230601.gappssmtp.com; s=20230601; t=1739977403; x=1740582203; 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=CwZwT7ivdJ3tTCtqQkgqeQk9fBkS2ZQ2TFkV2Mo8Kvg=; b=NGYJNnlhznKoIWynQ+KrN54SLitnI2H99x6JvFiedVVTsmwdHfpneEv+iUhGJyOa7z G2BKxEJ2/kOVcjNKQgP+NSQW+FChqPxS3hEP8d3uQNg/c0zybyIvUT+hf46PxXeUBP1X Uk9G2DpIn8YCnNy+2gs0Og0YQbmzH26o+8HWa7m4ZWL1wrl7jD6dKuyyPR3TcZUghoOi uNrYYIsChibP2veqsxVxEWxIA0FXG5rwfvaWIqQd+mK0GXYEep+Ik3CG5nd3Iy3c2j5g bzyX20FICGcKKLmR1cf8ypgTplSgGMAwCap9sh89ue66Wewwmz0D/cNhuKvo3Lb+XllE Uqjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1739977403; x=1740582203; 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=CwZwT7ivdJ3tTCtqQkgqeQk9fBkS2ZQ2TFkV2Mo8Kvg=; b=jq7U1gFKQ5Oj3iYkkwGiblK6t19ar2lEvEQYUuz52Pqjfp1xDqA2Fvmi1TbwSeH6i2 AnsL+4pKksfdu1Z1M5sv8GYKFNzyOnMoM9+DtX1RHA+AaCObeXSN25358TwwZu6w6ylq misTjLcO51McV5ouYOOM9yJcHa+qgF5kXXpkKLRdIKia82XrEhsbphFyM6ueMr4ToQi2 PyBpgTH2mN/0Kc7JmwwhB2zI6wv+DyF+jQGopwTh++Y/mSTc5wXWGOU9pRlIvowgi3ew jJsFvJGq7m27NADIXVqNP34D00/RsQsGgNxTV0nb2GThBqJVkEJvEtgSu+bk7i9f5GZb 9p+w== X-Gm-Message-State: AOJu0YwVWy21qY3qJR9ODxu7GeGzg12JUWPhQlHAp6qvrmzS0IXi66uB FJl+u7DIaum4gTZoTRTBlVPE3w+JH8lBj5NMpdqmLV3ENipibCOBIr+kFvRszNI= X-Gm-Gg: ASbGncvYPZJTeeXlPx+3LAHeOMZP8EkrryouQ8eIJZYAztD7Fg3HVgXh/iCT4vc8pKm z9ol9Wxo5T3t+jKlr6xmvs5FkUDKsKJB6kgdR8ZcgMjccrif03qaL5IiO0F1l0VBd1sgO5Re6PZ woQsAnrdivyuhC/I9HiahF6U2aOdZ7elVtwPDlDMu/eqvzsSSp4KXJJSd51Bz+NNa3nfjMbGa3U c4L2QGUjU2dM/DLowWGnC1MA6frtcdrRnt3i85wKjY2mf/bC4HEttpj0fBQw5LU08PTAPKgMQNv NGEkYM936yzFLlSdDXmyLkoBLCSKgsN5arrGXNJOL4UkuRt8uxKkHzvqiWcTSmNLSktS X-Google-Smtp-Source: AGHT+IHuf5HdvcZpmhbuSUgSvW5EKjWSEhiL9MJaibCMGwiaPoxvZ+EZ9fX1NZTmG6qGr4+nAk2pXw== X-Received: by 2002:a17:90b:3c82:b0:2f2:3efd:96da with SMTP id 98e67ed59e1d1-2fcb5a9d30fmr6384706a91.24.1739977402880; Wed, 19 Feb 2025 07:03:22 -0800 (PST) Received: from hermes.local (204-195-96-226.wavecable.com. [204.195.96.226]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2fc13b91424sm12017243a91.31.2025.02.19.07.03.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 19 Feb 2025 07:03:22 -0800 (PST) Date: Wed, 19 Feb 2025 07:03:20 -0800 From: Stephen Hemminger To: Lucas Cc: users@dpdk.org Subject: Re: Increase DPDK's virtual memory to more than 512 GiB Message-ID: <20250219070320.447ba505@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org On Wed, 19 Feb 2025 15:22:46 +0100 Lucas wrote: > Hello, > > I am creating an application where I want to cache packets in a ring for a > certain duration. To do so at high speed (100 Gb/s) for tens of seconds, I > would like to create a mempool with a size bigger than 500 GiB. > I know that in rte_config.h, we have this excerpt: > ``` > #define RTE_MAX_MEMSEG_LISTS 128 > ... > #define RTE_MAX_MEM_MB_PER_LIST 32768 > ``` > 4'194'304 MiB of addressable memory, which is more than enough. However, > there is a virtual memory limit on DPDK processes on x86_64, which appears > to be 512 GiB. > at https://doc.dpdk.org/guides/prog_guide/env_abstraction_layer.html it is > listed that RTE_MAX_MEM_MB controls that. > In the meson.build file in the config directory, we have: > ``` > if dpdk_conf.get('RTE_ARCH_64') > dpdk_conf.set('RTE_MAX_MEM_MB', 524288) > else # for 32-bit we need smaller reserved memory areas > dpdk_conf.set('RTE_MAX_MEM_MB', 2048) > endif > ``` > Changing this value does not seem to change the amount of virtual memory > that DPDK allocates. It appears that no headers or C-files actually > reference this value. > What would I need to change to allow more virtual memory than 512 GiB and > be able to allocate a mempool with a size bigger than that? > > Thank you in advance for any pointers! > > Kind regards, > Lucas Crijns Mempools come from huge pages. Do you have that many huge pages available?