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 71C6643FB0; Sun, 5 May 2024 11:35:57 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 42EE84028C; Sun, 5 May 2024 11:35:57 +0200 (CEST) Received: from mail-lf1-f44.google.com (mail-lf1-f44.google.com [209.85.167.44]) by mails.dpdk.org (Postfix) with ESMTP id C1B764025D for ; Sun, 5 May 2024 11:35:55 +0200 (CEST) Received: by mail-lf1-f44.google.com with SMTP id 2adb3069b0e04-51fdc9af005so1552474e87.3 for ; Sun, 05 May 2024 02:35:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714901755; x=1715506555; 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=Uwd8gKdbnGz0f9y9OrQ2nTwlt5UARW9bxmWt/hypSkQ=; b=HqBnmgdebHEOV+M0b0lzBBra2i0wMSUkztm1Q0rnSyBWPCqnxdu03wckOT9xHnGVa6 g8znGPl1wcufe7SfaqgkTTTLnaZc32FkHsxHF4RfbynJYB3StcpJAPuMujCaHWwEz8L/ QuDPNarVXUMRsz/KCMLqUUdHknQvAhXXFlYiDBOCPPU4SLuvULVq2oFS0tZcOzckqxFR PDgzA1ljjsGTxWyShnHI420GZ37ATq6F/WnrBxSH6lS6Kj5xZXpyBvyI/tqvNumylWoT 0EIeVxnIsbnIuUh+7uxbUORhmjlGFDiU7xENr6C/Nws2ZhWzsx0Iye8qMFVVQa4mOz1d 2tWA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714901755; x=1715506555; 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=Uwd8gKdbnGz0f9y9OrQ2nTwlt5UARW9bxmWt/hypSkQ=; b=gWWt7DtKWT9NU+u1DgYqYSe5slKLDWNVDTN3oVvm75WcLV3TruBrNbvk6gQGy2A4EV zXUQHdk0TEzRiFCh0pIKnCt4CDYXyslUyZVN67A0M0/1Y6aA7/eo6SshH0Ah15wOZB2y CdUCFc/kHdjhrzqON/bUXnpYkqnEAWi7CdHyayoGdVUMlzaUUrZn6zfqAhWipFSQsDif 3EwJOH3Aq4HNf5ItJ4O/zA+o1oFC9yMxMkRo4qi8C9BwWtUit2vqlybALgJ2zGoa5UlR okA6p6zqArhjPyf7pCuYucr/VdbdZ6eV4Lq1jeEOjnrXEgpTL+B7ffQeg3IF+caDG9qk d2Vg== X-Gm-Message-State: AOJu0YzOk5O6hSBTSspNDn8Zh7L9nFdgvEUNfC+2TlwRRQvvS1FxLh3w zm88xfIPpuHR/+UQvg0r6PEtmQveujkDTtQCVyf9HRHbzPOBWICPTZRRgg== X-Google-Smtp-Source: AGHT+IG0VjFJ7TVmnj16E4ozuS6/erdVe6IN8NKcm5+hLDTRrMQt03F9veiPHoBYcdtFN99lOORX1Q== X-Received: by 2002:a05:6512:548:b0:51d:3256:5327 with SMTP id h8-20020a056512054800b0051d32565327mr5796309lfl.35.1714901754693; Sun, 05 May 2024 02:35:54 -0700 (PDT) Received: from sovereign (broadband-109-173-110-33.ip.moscow.rt.ru. [109.173.110.33]) by smtp.gmail.com with ESMTPSA id x19-20020a056512079300b00518da444121sm1179292lfr.123.2024.05.05.02.35.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 05 May 2024 02:35:53 -0700 (PDT) Date: Sun, 5 May 2024 12:35:51 +0300 From: Dmitry Kozlyuk To: "Lombardo, Ed" Cc: "dev@dpdk.org" Subject: Re: Need help with reducing VIRT memory Message-ID: <20240505123551.6569236a@sovereign> In-Reply-To: References: <20240502230352.7bb1ef0d@sovereign> <20240503235442.70b4b056@sovereign> <20240503235632.27ea47f4@sovereign> X-Mailer: Claws Mail 3.18.0 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 2024-05-05 03:25 (UTC+0000), Lombardo, Ed: > Hi Dmitry, > I tried your settings tonight and the application VIRT memory is now 7.9G and is in the ball park, you are amazing. > > #define RTE_MAX_MEMSEG_LISTS 2 > #define RTE_MAX_MEMSEG_PER_LIST 1024 > #define RTE_MAX_MEM_MB_PER_LIST 2048 > #define RTE_MAX_MEMSEG_PER_TYPE 1024 > #define RTE_MAX_MEM_MB_PER_TYPE 2048 > > There is no possibility to change these settings at run-time? Maybe I > asking too much? Maybe would be something DPDK developers can consider? DPDK has a general aim to convert options from compile-time to run-time. However, these options would be considered in the last place if ever, because high VIRT consumption has never been considered harmful before. If you provide a detailed description of your use case and explain how and why this interferes with your application needs, the community can consider this rationale. Technically, these options are easy to be made dynamic.