DPDK patches and discussions
 help / color / mirror / Atom feed
From: Robert Nie <robertnie@live.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] about IOVA and namespace in DPDK 19.05
Date: Wed, 1 May 2019 23:31:18 +0000	[thread overview]
Message-ID: <CY4PR02MB2439837CA352EF767FF6AFC5DD3B0@CY4PR02MB2439.namprd02.prod.outlook.com> (raw)
Message-ID: <20190501233118.pRvVQi9k0y7b94ByBpEzUBpA2q-GlQ-JmlXQHqcg-OI@z> (raw)

Hello,

I am take a trial on AF_XDP feature of 19.05-rc2. I encountered two problems. One is about "iova-mode", another is about attaching bpf prog onto interface of specified namespace (probably new feature?)

I created a VM using uvt-tool, release=eoan, cpu=8, mem=8G, with host-passthrough enabled, and set vm.nr_hugepages = 2500. And then create 2 docker containers. And then run testpmd with parameters "--vdev net_af_xdp_a,iface=veth055cc57,queue=0 --vdev net_af_xdp_b,iface=veth438434b,queue=0", where veths are host side interface names of two containers. Finally I got following error,
xdp_umem_configure(): Failed to reserve memzone for af_xdp umem.
eth_rx_queue_setup(): Failed to configure xdp socket
Fail to configure port 0 rx queues
After some digging, I fixed it by using "--iova-mode=va". Would anyone please let me know if it was safe to use "va" instead of "pa" for veth use case? Or any performance drops?

Secondly, I'd like to attach bpf prog onto interface inside container, e.g. "lo" interface, so that my code can verdict the traffic between containers inside a pod. Then the testpmd arguments would be like "--vdev net_af_xdp_a,namespace=<NS>,iface=NAME,queue=0". Do you think this feature is doable and meaningful?


Thanks,
Robert Nie






             reply	other threads:[~2019-05-06 19:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-01 23:31 Robert Nie [this message]
2019-05-01 23:31 ` Robert Nie
2019-05-07 12:02 ` Burakov, Anatoly
2019-05-07 12:02   ` Burakov, Anatoly
2019-05-07 18:15   ` Robert Nie
2019-05-07 18:15     ` Robert Nie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CY4PR02MB2439837CA352EF767FF6AFC5DD3B0@CY4PR02MB2439.namprd02.prod.outlook.com \
    --to=robertnie@live.com \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).