From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Gadre Nayan <gadrenayan@gmail.com>
Cc: users@dpdk.org, dev@dpdk.org, ferruh.yigit@intel.com,
remy.horton@intel.com
Subject: Re: [dpdk-dev] [dpdk-users] Get interface speed through IOCTL
Date: Wed, 22 Jun 2016 14:31:45 +0200 [thread overview]
Message-ID: <3723042.ZWhDuQsRp0@xps13> (raw)
In-Reply-To: <CAKJ7aR43jj2Vhs4Bhswg0-js30K5B1NeWThvnnoQ_UHEh1jBtg@mail.gmail.com>
2016-06-22 17:49, Gadre Nayan:
> I need to get the interface speed though standard IOCTL call:
[...]
>
> However, for 10G interface I do not read a correct speed, since it may
> not be supported.
Yes
> Out 1G cards are I350 and 10G card is I40.
[...]
> There is no support for 10000base. So to get the ioctl working for 10G
> card, is it a trivial change of adding few more support options and
> adding another case SPEED_10000 clause, or is it more involved ?
You are talking about KNI which has some old ethtool support for
some igb and ixgbe NICs.
My opinion is that we should drop this ethtool support which do not
compile everywhere and has a very limited support.
If you want to get the speed information, you have several other ways
to explore:
- communicating with the DPDK application
- make a secondary application process
- add the feature in the secondary process app/proc_info
- use examples/ethtool (and check if it can be promoted in lib/)
- implement a kernel module upstream
If you just need to get the speed info, I feel app/proc_info would be
a good idea.
parent reply other threads:[~2016-06-22 12:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAKJ7aR43jj2Vhs4Bhswg0-js30K5B1NeWThvnnoQ_UHEh1jBtg@mail.gmail.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=3723042.ZWhDuQsRp0@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gadrenayan@gmail.com \
--cc=remy.horton@intel.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).