From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: KNI performance is not what is claimed Date: Thu, 20 Sep 2018 11:10:55 -0700 Message-ID: <20180920111055.54d32242@xeon-e3> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit To: dev@dpdk.org Return-path: Received: from mail-pl1-f171.google.com (mail-pl1-f171.google.com [209.85.214.171]) by dpdk.org (Postfix) with ESMTP id 2061F1B139 for ; Thu, 20 Sep 2018 20:11:04 +0200 (CEST) Received: by mail-pl1-f171.google.com with SMTP id ba4-v6so4709125plb.11 for ; Thu, 20 Sep 2018 11:11:04 -0700 (PDT) Received: from xeon-e3 (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id u25-v6sm34206176pfk.177.2018.09.20.11.11.02 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Thu, 20 Sep 2018 11:11:02 -0700 (PDT) List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" I wonder if KNI is claiming performance that was never measured on current CPU, OS, DPDK. With single stream and TCP testing on IXGBE (DPDK), I see lowest performance with KNI. Rx Tx KNI 3.2 Gbit/sec 1.3 Gbit/sec TAP 4.9 4.7 Virtio 5.6 8.6 Perhaps for 18.11 we should change documentation to remove language claiming better performance with KNI, and then plan for future deprecation?