From: Pilar Manzanares <pimanlonoct@gmail.com>
To: dev@dpdk.org
Subject: pipeline port in /port out error (swx)
Date: Wed, 8 Jun 2022 21:14:26 +0200 [thread overview]
Message-ID: <CAHTJm9-tpNCAPer3qn5pKyC3MVHroF_4NfhqwOe0wXOfdcgL1g@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1437 bytes --]
Hello,
I'm using dpdk-22.03 in an Ubuntu 20.04 Virtual Machine using VirtualBox.
Two network devices are binded.
./usertools/dpdk-devbind.py --status
Nework devices using DPDK-compatible driver
0000:00:08.0 "8254EM Gigabit........" drv=uio_pci_generic
unused=e1000,vfio-pci
0000:00:09.0 "8254EM Gigabit........" drv=uio_pci_generic
unused=e1000,vfio-pci
I am testing the pipeline application and the given examples
(registers.cli, l2fwd.cli...),
but the pipeline port in / port out commands always fail.
For example, testing
dpdk-pipeline -l0-1 -- -s ./examples/pipeline/examples/registers.cli
mempool MEMPOOL0 buffer 2304 pool 32K cache 256 cpu 0 -> OK
link LINK0 dev 0000:00:08.0 rxq 1 128 MEMPOOL0 txq 1 512 promiscouos on ->
OK
link LINK1 dev 0000:00:09.0 rxq 1 128 MEMPOOL0 txq 1 512 promiscouos on ->
OK (also checked using "link show")
pipeline PIPELINE0 create 0 -> OK
pipeline PIPELINE0 port in 0 link LINK0 rxq 0 bsz 32 --> port in error
pipeline PIPELINE0 port in 1 link LINK1 rxq 0 bsz 32 --> port in error
pipeline PIPELINE0 port out 0 link LINK0 txq 0 bsz 32 --> port out error
pipeline PIPELINE0 port out 1 link LINK1 txq 0 bsz 32 --> port out error
rte_swx_ctl_pipeline_port_in_config(p->p, port_id,"ethdev",¶ms) returns
-22 (EINVAL) incorrect values
The same happens testing l2fwd_mac_swap_pcap.cli which uses "source" and
"sink" types.
Any idea what is happening or how to solve it?
Thanks in advance
[-- Attachment #2: Type: text/html, Size: 1686 bytes --]
reply other threads:[~2022-06-13 7:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAHTJm9-tpNCAPer3qn5pKyC3MVHroF_4NfhqwOe0wXOfdcgL1g@mail.gmail.com \
--to=pimanlonoct@gmail.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).