From: Stephen Hemminger <stephen@networkplumber.org>
To: Stuart Xu <Stuart_Xu@symantec.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] How to identify a network port which is bound to DPDK
Date: Wed, 23 Aug 2017 09:53:57 -0700 [thread overview]
Message-ID: <20170823095357.581a6ccc@xeon-e3> (raw)
In-Reply-To: <F7426F33-9010-43B8-A751-EF24F91197A2@symantec.com>
On Tue, 22 Aug 2017 23:25:35 +0000
Stuart Xu <Stuart_Xu@symantec.com> wrote:
> Hi, I understand that the DPDK uses port_id to identify an Ethernet port. Is there a shell command to show a port’s status, such as link status and port ID etc. For non-DPDK bound port I can use tools like “ifconfig”. Does DPDK provide an “ifconfig” equivalent tool to check a port status?
>
DPDK network interfaces are not visible or controlled by kernel.
There are some ways to expose them i.e through KNI and some other proposed code.
next prev parent reply other threads:[~2017-08-23 16:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-22 23:25 Stuart Xu
2017-08-23 16:53 ` Stephen Hemminger [this message]
2017-08-23 19:35 ` [dpdk-users] [EXT] " Stuart Xu
2017-08-23 20:29 ` Stephen Hemminger
2017-08-24 16:22 ` Stuart Xu
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=20170823095357.581a6ccc@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=Stuart_Xu@symantec.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).