From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [dpdk-users] Get interface speed through IOCTL Date: Wed, 22 Jun 2016 14:31:45 +0200 Message-ID: <3723042.ZWhDuQsRp0@xps13> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: users@dpdk.org, dev@dpdk.org, ferruh.yigit@intel.com, remy.horton@intel.com To: Gadre Nayan Return-path: Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42]) by dpdk.org (Postfix) with ESMTP id C737BC12C for ; Wed, 22 Jun 2016 14:31:48 +0200 (CEST) Received: by mail-wm0-f42.google.com with SMTP id a66so3861587wme.0 for ; Wed, 22 Jun 2016 05:31:48 -0700 (PDT) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.