DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Deepak Gowda <deepak.dt06@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] xdp_umem_configure(): Failed to create umem
Date: Tue, 26 May 2020 10:14:02 +0100
Message-ID: <20200526091402.GA905@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <CAM84qfoQb0jhgsLbOPz655pv5aryoCfuu2WhGyxa056cAax7NQ@mail.gmail.com>

On Tue, May 26, 2020 at 11:27:10AM +0530, Deepak Gowda wrote:
> Hi All,
> I'm fairly new to xdp, i'm trying to run the testpmd with af_xdp. I have
> checked all the prerequisites for af_xdp.
> I see testpmd exiting with the following error,
> ./testpmd -c 0x3 -n 4 --vdev net_af_xdp0,iface=tap0 -- -i
> EAL: Detected 8 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: Selected IOVA mode 'PA'
> EAL: Probing VFIO support...
> EAL: PCI device 0000:00:03.0 on NUMA socket -1
> EAL:   Invalid NUMA socket, default to 0
> EAL:   probe driver: 1af4:1000 net_virtio
> EAL: PCI device 0000:00:0a.0 on NUMA socket -1
> EAL:   Invalid NUMA socket, default to 0
> EAL:   probe driver: 1af4:1000 net_virtio
> Interactive-mode selected
> testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=155456, size=2176,
> socket=0
> testpmd: preferred mempool ops selected: ring_mp_mc
> Warning! port-topology=paired and odd forward ports number, the last port
> will pair with itself.
> Configuring Port 0 (socket 0)
> *xdp_umem_configure(): Failed to create umemeth_rx_queue_setup(): Failed to
> configure xdp socket*
> Fail to configure port 0 rx queues
> EAL: Error - exiting with code: 1
>   Cause: Start ports failed
> Seems like xsk_umem__create() is failing, could this be a kernel issue?
> Before going further i wanted to confirm that my setup is fine and that
> there are no obvious mistakes, here is my setup details:
> debian buster kvm machine
> 4.19.0-9-amd64 kernel
> iface argument is a tap interface
> dpdk-stable-19.11.2
While I can't comment on the specific root cause of the issue you are
seeing, 4.19 is quite an old kernel for working with AF_XDP, since numerous
improvements and enhancements e.g. zero-copy support, have gone into the
kernel since then. I would generally recommend using a 5.4 or newer kernel
if working with AF_XDP.


      reply	other threads:[~2020-05-26  9:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26  5:57 Deepak Gowda
2020-05-26  9:14 ` Bruce Richardson [this message]

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:

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

  git send-email \
    --in-reply-to=20200526091402.GA905@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=deepak.dt06@gmail.com \
    --cc=dev@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git