* [dpdk-stable] [PATCH 2/5] mem: fix config name in error logs
[not found] <20201022220525.1532249-1-thomas@monjalon.net>
@ 2020-10-22 22:05 ` Thomas Monjalon
2020-10-28 12:08 ` Burakov, Anatoly
0 siblings, 1 reply; 2+ messages in thread
From: Thomas Monjalon @ 2020-10-22 22:05 UTC (permalink / raw)
To: dev
Cc: ferruh.yigit, david.marchand, bruce.richardson, anatoly.burakov,
olivier.matz, ciara.power, akhil.goyal, fiona.trahe,
john.griffin, deepak.k.jain, stable
When introducing the new option CONFIG_RTE_MAX_MEM_MB_PER_TYPE,
some logs were referencing a wrong name: CONFIG_RTE_MAX_MEM_PER_TYPE.
Fixes: 66cc45e293ed ("mem: replace memseg with memseg lists")
Cc: stable@dpdk.org
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
lib/librte_eal/freebsd/eal_memory.c | 2 +-
lib/librte_eal/linux/eal_memory.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/librte_eal/freebsd/eal_memory.c b/lib/librte_eal/freebsd/eal_memory.c
index b8b337a554..8d4b26b9b8 100644
--- a/lib/librte_eal/freebsd/eal_memory.c
+++ b/lib/librte_eal/freebsd/eal_memory.c
@@ -174,7 +174,7 @@ rte_eal_hugepage_init(void)
if (msl_idx == RTE_MAX_MEMSEG_LISTS) {
RTE_LOG(ERR, EAL, "Could not find space for memseg. Please increase %s and/or %s in configuration.\n",
RTE_STR(CONFIG_RTE_MAX_MEMSEG_PER_TYPE),
- RTE_STR(CONFIG_RTE_MAX_MEM_PER_TYPE));
+ RTE_STR(CONFIG_RTE_MAX_MEM_MB_PER_TYPE));
return -1;
}
arr = &msl->memseg_arr;
diff --git a/lib/librte_eal/linux/eal_memory.c b/lib/librte_eal/linux/eal_memory.c
index 3e47efe582..df0f07ee7e 100644
--- a/lib/librte_eal/linux/eal_memory.c
+++ b/lib/librte_eal/linux/eal_memory.c
@@ -714,7 +714,7 @@ remap_segment(struct hugepage_file *hugepages, int seg_start, int seg_end)
if (msl_idx == RTE_MAX_MEMSEG_LISTS) {
RTE_LOG(ERR, EAL, "Could not find space for memseg. Please increase %s and/or %s in configuration.\n",
RTE_STR(CONFIG_RTE_MAX_MEMSEG_PER_TYPE),
- RTE_STR(CONFIG_RTE_MAX_MEM_PER_TYPE));
+ RTE_STR(CONFIG_RTE_MAX_MEM_MB_PER_TYPE));
return -1;
}
--
2.28.0
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-stable] [PATCH 2/5] mem: fix config name in error logs
2020-10-22 22:05 ` [dpdk-stable] [PATCH 2/5] mem: fix config name in error logs Thomas Monjalon
@ 2020-10-28 12:08 ` Burakov, Anatoly
0 siblings, 0 replies; 2+ messages in thread
From: Burakov, Anatoly @ 2020-10-28 12:08 UTC (permalink / raw)
To: Thomas Monjalon, dev
Cc: ferruh.yigit, david.marchand, bruce.richardson, olivier.matz,
ciara.power, akhil.goyal, fiona.trahe, john.griffin,
deepak.k.jain, stable
On 22-Oct-20 11:05 PM, Thomas Monjalon wrote:
> When introducing the new option CONFIG_RTE_MAX_MEM_MB_PER_TYPE,
> some logs were referencing a wrong name: CONFIG_RTE_MAX_MEM_PER_TYPE.
>
> Fixes: 66cc45e293ed ("mem: replace memseg with memseg lists")
> Cc: stable@dpdk.org
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-10-28 12:09 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <20201022220525.1532249-1-thomas@monjalon.net>
2020-10-22 22:05 ` [dpdk-stable] [PATCH 2/5] mem: fix config name in error logs Thomas Monjalon
2020-10-28 12:08 ` Burakov, Anatoly
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).