DPDK usage discussions
 help / color / mirror / Atom feed
From: Martin Trommer <Martin.Trommer@rohde-schwarz.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] Example app link_status_interrupt: interfaces come not up
Date: Fri, 20 Apr 2018 10:05:54 +0000	[thread overview]
Message-ID: <4e6d9a96cb5a4f79b7db2f2874d40601@rohde-schwarz.com> (raw)

Hello DPDK users,


If I start the DPDK sample application "link_status_interrupt" the interface states will not change. It stays DOWN. App is exited by sending Signal SIGINT.

A second start of "./link_status_interrupt" will show the interface states as UP.

A third start will also show the interface states as UP.


Here my command:

./link_status_interrupt -w 0000:18:00.2 -w 0000:18:00.3 -l 0-2 -- -q 2 -p 3

0000:18:00.2 and 0000:18:00.3 are wired with each other.
I use a X710 on board chip with 4 interfaces (0000:18:00.0 - 0000:18:00.3).

DPDK 18.02 is used.


What can I do that the interfaces will come UP in the first run ?


Thanks in advance,

Martin

                 reply	other threads:[~2018-04-20 10:05 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=4e6d9a96cb5a4f79b7db2f2874d40601@rohde-schwarz.com \
    --to=martin.trommer@rohde-schwarz.com \
    --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).