From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Trybula, ArturX" <arturx.trybula@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "shallyv@marvell.com" <shallyv@marvell.com>,
"akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eal: improve user notification for too low memzone segments
Date: Mon, 16 Dec 2019 16:05:01 +0000 [thread overview]
Message-ID: <BN6PR11MB1796EEDB568C46070769056EE4510@BN6PR11MB1796.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20191216154406.3827-1-arturx.trybula@intel.com>
Including Anatoly as maintainer for lib/librte_eal/common/eal_common_mem*
> -----Original Message-----
> From: Trybula, ArturX <arturx.trybula@intel.com>
> Sent: Monday, December 16, 2019 3:44 PM
> To: dev@dpdk.org; Trahe, Fiona <fiona.trahe@intel.com>; shallyv@marvell.com; Dybkowski, AdamX
> <adamx.dybkowski@intel.com>; Danilewicz, MarcinX <marcinx.danilewicz@intel.com>; Trybula, ArturX
> <arturx.trybula@intel.com>; akhil.goyal@nxp.com
> Subject: [PATCH] eal: improve user notification for too low memzone segments
>
> In case of too low number of memzone segements user notification
> was misleading. This patch improves the description by providing
> better explanation about the cause.
>
> Signed-off-by: Artur Trybula <arturx.trybula@intel.com>
> ---
> lib/librte_eal/common/eal_common_memzone.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/librte_eal/common/eal_common_memzone.c
> b/lib/librte_eal/common/eal_common_memzone.c
> index 99b8d6531..c1acbbb3c 100644
> --- a/lib/librte_eal/common/eal_common_memzone.c
> +++ b/lib/librte_eal/common/eal_common_memzone.c
> @@ -71,7 +71,7 @@ memzone_reserve_aligned_thread_unsafe(const char *name, size_t len,
>
> /* no more room in config */
> if (arr->count >= arr->len) {
> - RTE_LOG(ERR, EAL, "%s(): No more room in config\n", __func__);
> + RTE_LOG(ERR, EAL, "%s(): Number of requested memzone segments exceeds
> RTE_MAX_MEMZONE\n", __func__);
> rte_errno = ENOSPC;
> return NULL;
> }
> --
> 2.17.1
next prev parent reply other threads:[~2019-12-16 16:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 15:44 Artur Trybula
2019-12-16 16:05 ` Trahe, Fiona [this message]
2019-12-20 15:08 ` [dpdk-dev] [PATCH v2 0/1] eal: user notification improvement Artur Trybula
2019-12-20 15:08 ` [dpdk-dev] [PATCH v2 1/1] eal: improve user notification for too low memzone segments Artur Trybula
2020-01-14 10:40 ` Burakov, Anatoly
2020-01-20 17:53 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BN6PR11MB1796EEDB568C46070769056EE4510@BN6PR11MB1796.namprd11.prod.outlook.com \
--to=fiona.trahe@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=anatoly.burakov@intel.com \
--cc=arturx.trybula@intel.com \
--cc=dev@dpdk.org \
--cc=shallyv@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).