From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 346] Set the link speed / duplex of a DPDK port
Date: Tue, 10 Sep 2019 09:10:28 +0000 [thread overview]
Message-ID: <bug-346-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=346
Bug ID: 346
Summary: Set the link speed / duplex of a DPDK port
Product: DPDK
Version: unspecified
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: enhancement
Priority: Normal
Component: ethdev
Assignee: dev@dpdk.org
Reporter: tohofman@cisco.com
Target Milestone: ---
Hello community,
strictly speaking this is not a bug but I need help in figuring out how to set
the link speed and the duplex settings of a DPDK port.
I did some research and came to the following results:
* For a non-DPDK port, there is ethtool however this only works for ports in
the kernel space.
I saw that there is a DPDK Kernel NIC Interface (KNI) that allows the use of
the ethtool for DPDK ports however it says that it currently only provides
minimal ethtool functionality such as querying but not changing link settings.
* I also discovered that the testpmd application offers a runtime function to
set the speed and duplex mode for a DPDK port but if I understood it correctly
this app is designed to test DPDK and not to manage port settings. So I'm not
sure if I can use it to change the link speed / duplex in a persistent way.
Is anyone aware of a way to manage the DPDK port speed and duplex systemwide?
Does it perhaps work with any of the aforementioned applications and I just
overlooked something?
I would be very pleased about any ideas!
Thanks in advance.
Tobias
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-09-10 9:10 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=bug-346-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).