Our preference is to have native drivers, that is what we did already for many devices. DPDK is not modular so each time you want ot use some DPDK feature end up with sub optimal solution. Notable exception is DPDK crypto which allows use of crypto PMDs without being forced to use mbufs, etc...
I’m not very familiar with DPDK AF_XDP pmd, but my guess is that if it is not working, likely it is because it needs to do something special with buffer memory (i.e. register regions trough AFXDP APIs) and that memory is handled by VPP. > On 18.05.2021., at 11:25, Catalin Vasile <[email protected]> wrote: > > So shouldn't this hack for also using the vpp buffer manager be generally > usable with all PMDs? > From: Damjan Marion <[email protected]> > Sent: Tuesday, May 18, 2021 1:17 > To: Catalin Vasile <[email protected]> > Cc: [email protected] <[email protected]> > Subject: Re: [vpp-dev] [DPDK] AF_XDP PMD > > > No, dpdk PMDs are also using vpp buffer manager, we are cheating a bit by > registering fake mempool. > > — > Damjan > > > On 17.05.2021., at 23:40, Catalin Vasile <[email protected]> wrote: > > > > �쏜㷃�쏜㷃�쏜㋢鹋ᢢ燨꽹ꥥ駫ⱪެ뇩譡諈⮢觬㽅죩瞵皆�돿쭬緘ꣾꚗ庿咽닆ꁻﵽ�貺힓蘫Ꭲ颜蛛榳￥請汽�﹫翳漷㛿껹蚮让㬉�響痫ﺣ깘겶쟝誅➲犸魺᭭ꛏﾖ⬭뇷抣뺚嵺￮黋魶暫誉쨦�쏜㷃�쏜㷃�쏜
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19396): https://lists.fd.io/g/vpp-dev/message/19396 Mute This Topic: https://lists.fd.io/mt/82836782/21656 Group Owner: [email protected] Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
