From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: [PATCH 0/6] net/tap: fixes and cleanups Date: Fri, 11 Jan 2019 10:06:53 -0800 Message-ID: <20190111180659.5972-1-stephen@networkplumber.org> Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Cc: Stephen Hemminger To: dev@dpdk.org Return-path: Received: from mail-pf1-f193.google.com (mail-pf1-f193.google.com [209.85.210.193]) by dpdk.org (Postfix) with ESMTP id 3BF721BA5D for ; Fri, 11 Jan 2019 19:07:09 +0100 (CET) Received: by mail-pf1-f193.google.com with SMTP id u6so7279720pfh.11 for ; Fri, 11 Jan 2019 10:07:09 -0800 (PST) List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" The tap device (used by vdev_netvsc on Azure) has a bug that prevents it working with primary/secondary process model because the device name generation assumed a single process. The fix for this is to have the kernel assign the device name (patch #5). While investigating this, found a number of other small issues that should be cleaned up as well. Stephen Hemminger (6): net/tap: use strlcpy for interface name net/tap: allow full length names net/tap: check interface name in kvargs net/tap: lower the priority of log messages net/tap: let kernel choose tun device name net/tap: get rid of global tuntap_name drivers/net/tap/rte_eth_tap.c | 106 +++++++++++++++++++++------------- 1 file changed, 65 insertions(+), 41 deletions(-) -- 2.20.1