From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 99EB91B2C8; Fri, 26 Jan 2018 18:00:33 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 33B0B2104F; Fri, 26 Jan 2018 12:00:33 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 26 Jan 2018 12:00:33 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=Vn6WalrND/NGO3ALGkZc+w+8u2 /vdLx4IKOKJIDP390=; b=O2iB0jcxqEoFuKqSo7dW42FroXmrbLXuaYMF71IT2h U+/lRGPl1Ern0RuaeateLAlNs2PBQ9ZzFOWnVX++cckm+T5pf4BpbyppD0QNr3lT SWQRV/Am6h7a/0o5g6KRavf3/sWFvIHtZ2Cbxrq/HbLhHnmEwHwz3XflwJ6BWHnS s= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Vn6Wal rND/NGO3ALGkZc+w+8u2/vdLx4IKOKJIDP390=; b=FzdCJUkPBtHfyR3LslkZPD 2ODhdJR91/E5/yaxBC45xTb9oXnZqmP6cfVjcSA6hOFTFOdh3sPLZY01/1odRZHj A2e7/cWe6DxkmWpljKKiAyn7NH+XGZcg8xMkEDs754IcdfPqMcpafpxykLvOR+RI SHe8kQiTbpxQPdYUwO90APLcL9htkXDhc8wLamFiZtL48RkkNxkmLuKTJlfFG+hT NwQO1DjdWIKoUzbWpA/HSCqlBQCvU7N21QeB+V8G6w7e+YMUVcBuirVtEjHjtUrX CyQep0mo0RXFtwqWtG25WRbwF61kMge/RNRbj9N17ABIDEOKydZ5D+Ux4Q6kIPqA == X-ME-Sender: <xms:sV5rWjK2_UHcsqKvvz8YvT1SACxiziHs8KKXIsAYq7YZw4iZHGg6Ow> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id CB98A24550; Fri, 26 Jan 2018 12:00:32 -0500 (EST) From: Thomas Monjalon <thomas@monjalon.net> To: Vipin Varghese <vipin.varghese@intel.com>, harry.van.haaren@intel.com Cc: stable@dpdk.org, dev@dpdk.org Date: Fri, 26 Jan 2018 17:59:47 +0100 Message-ID: <1543040.UXSxQDX3pr@xps> In-Reply-To: <1515700054-29654-1-git-send-email-vipin.varghese@intel.com> References: <1514735641-8738-1-git-send-email-vipin.varghese@intel.com> <1515700054-29654-1-git-send-email-vipin.varghese@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v2] app/procinfo: Fix memory leak by rte_service_init X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Fri, 26 Jan 2018 17:00:33 -0000 11/01/2018 20:47, Vipin Varghese: > When procinfo is run multiple times against primary application, it > consumes huge page memory by rte_service_init. Which is not released > at exit of application. > > Invoking rte_service_finalize to real memory and prevent memory leak. I don't think it is correct to call rte_service_finalize in applications, while rte_service_init is called in EAL. Maybe we need a new function in EAL.