Looks like your are running an old vPP… You can check phymem allocation by running CLI:
vpp# show physmem vpp# show dpdk physmem The master code is managing phymem by itself, in other words, allocating buffers from huge pages hold by vPP instead of DPDK. Typically, it will use 2 huge pages unless you want many buffers per numa. Regards, Kingwel From: [email protected] <[email protected]> On Behalf Of siddarth rai Sent: 2019年3月25日 20:27 To: [email protected] Subject: [vpp-dev] Contribution of DPDK plugin in VPP virtual memory size Hello, I was trying to figure out the contribution of different components in Virtual Memory Size of VPP. I am using pmap -x to check this I see that the heap size directly contributes to it. I am using the DPDK plugin and I can see dpdk_mbuf_pool taking up 1.2 GB per socket (no of mbuffs 500K per socket). 00002aaaaac00000 1220608 0 0 rw-s- dpdk_mbuf_pool_socket0 00002aaaf5400000 1220608 0 0 rw-s- dpdk_mbuf_pool_socket1 However, I see around 4GB memory being consumed by something anon. This goes away as soon as I disable dpdk plugin. 00002b0668000000 4194304 0 0 ----- [ anon ] Can anyone tell me how is DPDK plugin using this extra 4 GB memory ? Any help will be much appreciated. Regards, Siddarth
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12636): https://lists.fd.io/g/vpp-dev/message/12636 Mute This Topic: https://lists.fd.io/mt/30749806/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
