From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier MATZ Subject: Re: [PATCH v3 1/2] eal: allow user to override default pool handle Date: Mon, 4 Sep 2017 13:46:36 +0200 Message-ID: <20170904114635.tgx6m6xr353dxrzt@neon> References: <20170720070613.18211-2-santosh.shukla@caviumnetworks.com> <20170815080717.9413-1-santosh.shukla@caviumnetworks.com> <20170815080717.9413-2-santosh.shukla@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org, thomas@monjalon.net, jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com To: Santosh Shukla Return-path: Received: from mail.droids-corp.org (zoll.droids-corp.org [94.23.50.67]) by dpdk.org (Postfix) with ESMTP id 1730B37A0 for ; Mon, 4 Sep 2017 13:46:44 +0200 (CEST) Content-Disposition: inline In-Reply-To: <20170815080717.9413-2-santosh.shukla@caviumnetworks.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" Hi Santosh, On Tue, Aug 15, 2017 at 01:37:16PM +0530, Santosh Shukla wrote: > --- a/lib/librte_eal/common/eal_internal_cfg.h > +++ b/lib/librte_eal/common/eal_internal_cfg.h > @@ -83,6 +83,7 @@ struct internal_config { > const char *hugefile_prefix; /**< the base filename of hugetlbfs files */ > const char *hugepage_dir; /**< specific hugetlbfs directory to use */ > > + char mbuf_pool_name[RTE_MBUF_POOL_OPS_NAMESIZE]; /**< mbuf pool name */ > unsigned num_hugepage_sizes; /**< how many sizes on this system */ > struct hugepage_info hugepage_info[MAX_HUGEPAGE_SIZES]; > }; > --- a/lib/librte_eal/common/include/rte_eal.h > +++ b/lib/librte_eal/common/include/rte_eal.h > @@ -54,6 +54,8 @@ extern "C" { > > /* Maximum thread_name length. */ > #define RTE_MAX_THREAD_NAME_LEN 16 > +/* Maximum length of mbuf pool ops name. */ > +#define RTE_MBUF_POOL_OPS_NAMESIZE 32 > To avoid to define a new constant, is there something preventing to use RTE_MEMPOOL_OPS_NAMESIZE? Or even better, is it possible to use a 'const char *', like it's done for hugepage_dir and hugepage_prefix? Thanks, Olivier