From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 01E25C4338F for ; Fri, 6 Aug 2021 19:05:23 +0000 (UTC) Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by mail.kernel.org (Postfix) with ESMTP id 5D598610E7 for ; Fri, 6 Aug 2021 19:05:22 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 5D598610E7 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dpdk.org Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 480D2410F9; Fri, 6 Aug 2021 21:05:21 +0200 (CEST) Received: from mail-lf1-f54.google.com (mail-lf1-f54.google.com [209.85.167.54]) by mails.dpdk.org (Postfix) with ESMTP id 852EF407FF for ; Fri, 6 Aug 2021 21:05:19 +0200 (CEST) Received: by mail-lf1-f54.google.com with SMTP id b6so3502075lff.10 for ; Fri, 06 Aug 2021 12:05:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=VgJbWyMkD8brLmWo0eoCmly36lLA4TFERdoP46WH8wY=; b=Fed+UvGYnp1hxh6D8c3979D7jJCyJJfCGyyjcIQGkqDFn81cmfytlyqX+MHyVIEaLV W4m5SbiD3y3TCoel2nej55TFB+W+qDGtON/wfbBkGMZCXnYCwTPP0uVEVL/d5ORlZ318 ZRzwZHGOsJqQYrm2RAlwgsXpLkMx8YJXy3PNqdnbYrqREUGWa7sbls8S/H4mNimur7EA b/cctJpMZMBIbUoLKeRCceejHOnC3tzpapA0MxkFbuP/R8W7OuxImdBtD4XUO2KDmsjm BVjIPmemt7z69sSqIZjY989pwiv5XW9ANtdXZ6vFW92i1xLtWLc5U6L0mNJGnODA4wu9 xeWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=VgJbWyMkD8brLmWo0eoCmly36lLA4TFERdoP46WH8wY=; b=c+4tKF9WPqNhgc81izaJo69+WxTy9LcJTyiSwjedUxxDOFyEQjLMAAaPPPpbvLEHbd THeY1mBWoMM/ihZAiowDbJjIgqt0M75nioewN2ameX9m8H1WFM5UbGYYLcu+/yhzWCc5 bHkxDTRGUTCDxU9UP9nc4fFBeR/JtfTJOVrNkwg3c6uMxAPy6eChIgnX36Sv3BKycCJI lj2lDWpNGxeQa80tMryFJZ5KHDnqYaVfbZ4WF7BBi794p5zlfp+kCwEfgG8SJ1mbG9qD ObquTlOfXxJAcRF4H/R9grLTAR0WypGdkWQ0nsa50OdHItTz9O2mWKJQWKCfC5ZATWCm xjvA== X-Gm-Message-State: AOAM531D4Y0kexbxfln26G7hDuHOOajI9sVicza26DP5Phdw04It4g/D NC2Y+ZT+2hSIRMnfNh22ALc= X-Google-Smtp-Source: ABdhPJxx8IK3700bc504jitiHN+J5C3Bb41dx/RZ/2s+Dv5jBKQnXFbbKGdhQmMC2mNknZxeYs6Gqw== X-Received: by 2002:a05:6512:53c:: with SMTP id o28mr8893408lfc.641.1628276718905; Fri, 06 Aug 2021 12:05:18 -0700 (PDT) Received: from sovereign (broadband-37-110-65-23.ip.moscow.rt.ru. [37.110.65.23]) by smtp.gmail.com with ESMTPSA id z1sm910139lfu.222.2021.08.06.12.05.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 06 Aug 2021 12:05:17 -0700 (PDT) Date: Fri, 6 Aug 2021 22:05:17 +0300 From: Dmitry Kozlyuk To: Gagandeep Singh Cc: "dev@dpdk.org" , "anatoly.burakov@intel.com" , Hemant Agrawal , Nipun Gupta Message-ID: <20210806220517.465e61b3@sovereign> In-Reply-To: References: X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] Query regarding EAL -m option 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 Sender: "dev" 2021-08-06 09:06 (UTC+0000), Gagandeep Singh: > Hi, > > I can understand "-m" option can be used in "-legacy-mode" to limit the memory reservation during the eal_init. > Is it true for dynamic memory allocation mode as well that dynamically allocated memory cannot be more than memory specified in "-m"? Or this option is valid only for legacy mode? > > Regards, > Gagab Hi Gagab, In any mode -m specifies how much memory to request from the OS during EAL startup. In legacy mode, this will be the maximum amount of memory DPDK can allocate. In dynamic mode, this is just initial amount that also will never be freed back to the system (while everything above this will).