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 2FC301B390
 for <dev@dpdk.org>; Mon, 29 Jan 2018 11:56:45 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id C63DF20A8B;
 Mon, 29 Jan 2018 05:56:44 -0500 (EST)
Received: from frontend1 ([10.202.2.160])
 by compute1.internal (MEProxy); Mon, 29 Jan 2018 05:56:44 -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=eRsmkYGAfEl8U6Siv3q3MV7l/U
 fogYF3iN+sp5wSi2c=; b=GzTTUOZhC9FQJ3A9uGeg1rHrTWaCGY1imkOAFjMA8z
 v8dIJ0w1YAUa3igvGJgSmay280gYzeuqY6OlPGbauyEIh42Hmty5kZHgHfDNadHZ
 rgc1/rZo5fckRQ8DacyeKolqtDQrN0dKSASDOtYRB6Hg2mToXulB/6BV7cWoGNP3
 E=
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=eRsmkY
 GAfEl8U6Siv3q3MV7l/UfogYF3iN+sp5wSi2c=; b=sIg5EYi3vC3e7/5B10D+r4
 xZNs6uUwYHKbS8jeHX6gcDjDZuky7vXbIWur6O3yVgSiCNcVWCGtuZ6clUkLmNYE
 mGltX/qlA/THqWFIlyuqqFEHCKptBuQhfi9D+bItYx+vEd9N4cpUEYFbGAkRIZK8
 45T15TYo4Gcoo1FwmAFjRpZOr+NUXSvLqpjPwGjb9v7RNVvG/oW6VzI51WouA9Iy
 cHNtMFEASTDrudw04UJ8J6LVgI7/p8UCtKNZUFh2Au8BS3yRrKMuQu/TWoYlYi/I
 KEDf/hgPvsgHRAHB24b375UdWrFcrrw9o2rAp1rK7PCySNl7vayUcr8veP3sckIw
 ==
X-ME-Sender: <xms:7P1uWmGN3dWCuvxK5BHIzueMpHDKzmxMI0S9K7zAnmhgoPzAohzKeA>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 88EB27E622;
 Mon, 29 Jan 2018 05:56:44 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Harry van Haaren <harry.van.haaren@intel.com>
Cc: dev@dpdk.org, vipin.varghese@intel.com
Date: Mon, 29 Jan 2018 11:55:58 +0100
Message-ID: <3800883.jMHuFJQnlm@xps>
In-Reply-To: <1517222751-110376-2-git-send-email-harry.van.haaren@intel.com>
References: <1517077877-53654-1-git-send-email-harry.van.haaren@intel.com>
 <1517222751-110376-1-git-send-email-harry.van.haaren@intel.com>
 <1517222751-110376-2-git-send-email-harry.van.haaren@intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH v2 2/4] eal: add function to release internal
	resources
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: Mon, 29 Jan 2018 10:56:45 -0000

29/01/2018 11:45, Harry van Haaren:
> --- a/doc/guides/prog_guide/env_abstraction_layer.rst
> +++ b/doc/guides/prog_guide/env_abstraction_layer.rst
> +Finalizing and Cleanup
> +~~~~~~~~~~~~~~~~~~~~~~
> +
> +During the initialization of EAL resources such as hugepage backed memory can be
> +allocated by core components.  The memory allocated during ``rte_eal_init()``
> +can be released by calling the ``rte_eal_finalize()`` function. Refer to the
> +API documentation for details.

About naming, what is better between
	rte_eal_finalize() and
	rte_eal_cleanup() ?
I tend to think that "cleanup" is more descriptive.