From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2 2/4] eal: add function to release internal resources Date: Mon, 29 Jan 2018 11:55:58 +0100 Message-ID: <3800883.jMHuFJQnlm@xps> 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-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, vipin.varghese@intel.com To: Harry van Haaren Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 2FC301B390 for ; Mon, 29 Jan 2018 11:56:45 +0100 (CET) In-Reply-To: <1517222751-110376-2-git-send-email-harry.van.haaren@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.