From: Stephen Hemminger <stephen@networkplumber.org>
To: 李勇 <1054946122@qq.com>
Cc: "dev" <dev@dpdk.org>
Subject: Re: dpdk rte_eth_rx_burst Failed to obtain data.
Date: Mon, 2 Sep 2024 09:40:16 -0700 [thread overview]
Message-ID: <20240902094016.549d944e@hermes.local> (raw)
In-Reply-To: <tencent_0DA66971113AA1B41F00575950F4DB759009@qq.com>
On Sat, 31 Aug 2024 09:44:21 +0800
"李勇" <1054946122@qq.com> wrote:
> I use the dpdk-23-11 version, system debian11, network card i210, CPU Cortex-A55. After the dpdk-23-11 service is compiled and installed, Start dpdk-23-11/examples/multi-process/cron_derve_mp/mp_derver/ build/mpuserver -l 1-2 -n 4 -- -p 1- n 1. Because dpdk only takes over one network card, I commented out the parameter restrictions in argc.c under mp_server. The mp_server service is started successfully. Procedure No data is displayed when a packet is sent through a network cable. Procedure But there is data with dpdk-testpmd. I have not encountered such a problem before and hope to get help.
Which network interface are you using? Some network drivers are broken in the Multi-process mode.
Are there any log messages on startup?
parent reply other threads:[~2024-09-02 16:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tencent_0DA66971113AA1B41F00575950F4DB759009@qq.com>]
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=20240902094016.549d944e@hermes.local \
--to=stephen@networkplumber.org \
--cc=1054946122@qq.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.