thanks. then those pools can be moved to dpdk socket-mem, I guess. I'll submit a patch soon.
-------- 原始邮件 -------- 主题： Re: [vpp-dev] dpdk socket-mem and dpdk_pool_create 来自： Damjan Marion <dmar...@me.com> 发至： 2018年11月25日 下午8:06 抄送： Kingwel Xie <kingwel....@ericsson.com> > On 25 Nov 2018, at 05:23, Kingwel Xie <kingwel....@ericsson.com> wrote: > > Hi Damjan and vPPers, > > I got a question about the physical mem management in vPP. > > As I understand, we specify socket-mem in startup.conf for DPDK to allocate > mem for itself, but we are using vPP phymem allocator for mbuf and crypto > PMDs if vdev is specified. The latter consist of crypto op , session, and > driver pools, and they are quite small in general. However, at least one > hugepage will be allocated for each pool, which could be 1GB. Big waste in a > way. > DPDK instead handles it in a better way using a mem segment based mechanism. > > Question: why use a customzied dpdk_pool_create instea of asking DPDK to > manage mempool just like rte_pktbuf_create_by_ops? > We care only for buffer mempools to be allocated by vpp physmem allocator, no need for others. They can be allocated by dpdk or alternatively other mempools can share single physmem region with dpdk buffer mempools.... -- Damjan
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11406): https://lists.fd.io/g/vpp-dev/message/11406 Mute This Topic: https://lists.fd.io/mt/28308134/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
