From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: NIC speed capabilities Date: Wed, 20 Jul 2016 17:19:15 +0200 Message-ID: <2151720.9kPUgdrJTB@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit To: dev@dpdk.org Return-path: Received: from mail-wm0-f50.google.com (mail-wm0-f50.google.com [74.125.82.50]) by dpdk.org (Postfix) with ESMTP id 9D3EE377C for ; Wed, 20 Jul 2016 17:19:17 +0200 (CEST) Received: by mail-wm0-f50.google.com with SMTP id q128so60648215wma.1 for ; Wed, 20 Jul 2016 08:19:17 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id v189sm31892564wmv.12.2016.07.20.08.19.16 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 20 Jul 2016 08:19:16 -0700 (PDT) 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" Hi drivers maintainers, The first line of the table in doc/guides/nics/overview.rst is outstandingly empty! Since the commit http://dpdk.org/commit/e274f57, it is possible to announce the speed capabilities of each port. The first implementation was only trying to fill some realistic values at the driver level. Please complete this work to have the exact values depending of the device model. Thank you