2022-09-23 12:12 (UTC+0000), Umakiran Godavarthi (ugodavar):
> [Uma] : Yes I agree if free_hp = 400, nr_hp = 252, we are expecting DPDK
> takes only 252 and keep the remaining pages free in its heap.
> As you have mentioned just boot DPDK with 1 page, and add
> pages we want later, is this the steps
>
> 1. NR_HP =1 , FREE_HP = 1
> 2. EAL INIT (DPDK boots up with 1 2 MB page)
> 3. What is the API for adding later on pages ? (rte_extmem_*, can you
> please give the full API details and how to call it with arguments )
Guide:
https://doc.dpdk.org/guides-19.11/prog_guide/env_abstraction_layer.html#support-for-externally-allocated-memory
I recommend reading the entire section about DPDK memory management
since you're going to use an uncommon API
and should understand what's going on.
API (the linked function and those following it):
http://doc.dpdk.org/api-19.11/rte__malloc_8h.html#a2295623c85ba41fe5bf7dce6bf0393d6
http://doc.dpdk.org/api-19.11/rte__memory_8h.html#a653510fb0c58bf63f54708677e3a2eba
> We can do 1,2,3 there is a problem once we reduce pages to 1 , kernel will
> free the huge pages totally
>
> So is there a way not to touch NR_HP, FREE_HP, and just pass arguments to
> boot DPDK with just 1 page ? Please let us know and later add pages we need
> to DPDK !!
See --socket-mem EAL option:
http://doc.dpdk.org/guides-19.11/linux_gsg/linux_eal_parameters.html#id3
> Why do you need legacy mode in the first place?
> Looks like you're painfully trying to achieve the same result
> that dynamic mode would give you automatically.
>
> [Uma] : Yes , we can’t avoid legacy memory design as secondary process mapped
> page by page to primary process , and physical addr space is same for both
> processes. We have to stick to legacy memory design only for now !!
Sorry, I still don't understand.
Virtual and physical addresses of DPDK memory are the same across processes
in both legacy and dynamic memory mode.
