From: Stephen Hemminger <stephen@networkplumber.org>
To: Anna Tauzzi <admin@argonnetech.net>
Cc: users@dpdk.org
Subject: Re: Initializing and starting port on primary but transmitting on secondary I get port not ready
Date: Wed, 31 Aug 2022 18:25:46 -0700 [thread overview]
Message-ID: <20220831182546.228d64a3@hermes.local> (raw)
In-Reply-To: <CAK_0FMTBmt_y1EHEZVR8qGJY6N14TAVH_VLvbnpYywee6=EUgw@mail.gmail.com>
On Wed, 31 Aug 2022 22:59:56 +0200
Anna Tauzzi <admin@argonnetech.net> wrote:
> I initialize a port with the following methods on a primary process:
>
> rte_dev_probe(vf)
>
> rte_eth_dev_configure(port_id, ... );
>
> rte_eth_dev_adjust_nb_rx_tx_desc(port_id, ... );
>
> rte_eth_rx_queue_setup(port_id, .... );
>
> rte_eth_tx_queue_setup(port_id, ... );
>
> rte_eth_dev_start(port_id ... );
>
>
>
> Then I use the rte_eth_tx_burst(port_id) in the secondary process but I get
> this message:
>
> called tx_pkt_burst for not ready port 0
>
> Is this expected?
No looks like a device driver bug. Which PMD?
next prev parent reply other threads:[~2022-09-01 1:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 20:59 Anna Tauzzi
2022-09-01 1:25 ` Stephen Hemminger [this message]
2022-09-01 7:33 ` Anna Tauzzi
2022-09-01 15:21 ` Stephen Hemminger
2022-09-05 10:14 ` Anna Tauzzi
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=20220831182546.228d64a3@hermes.local \
--to=stephen@networkplumber.org \
--cc=admin@argonnetech.net \
--cc=users@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).