From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 065F8A00E6 for ; Fri, 17 May 2019 20:46:51 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B8DFD5B1E; Fri, 17 May 2019 20:46:50 +0200 (CEST) Received: from mail-pl1-f179.google.com (mail-pl1-f179.google.com [209.85.214.179]) by dpdk.org (Postfix) with ESMTP id 25DEE2BA5 for ; Fri, 17 May 2019 20:46:49 +0200 (CEST) Received: by mail-pl1-f179.google.com with SMTP id f97so3727424plb.5 for ; Fri, 17 May 2019 11:46:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=dpfF2HhLnCWh+A/rvJGLNLONlxYRdj17TeegRGUkPTM=; b=W/3afoAziUQdZszd9qgLG62QdRFPeukc8bp7GnTHRDu0iMo5rRrk87it5KjWCzZ/ww OyTl+hKyGh+QHz56jrlOYh48/xG+D1aTUVLzObHfbu0v4a6TLCMKpzrmlmFtbSVnmhHC DB1xznNgpfj1hXCjKf624x211jkfma+BZG1eXWpwvoCosI6/HX3+954PKUP/XmQSuLia c8QywQDlKAaBdTRIbj/a47K5dLewiGbR3/k6t+rGoA+afHdAa3TetdgAtfxp79XXXcJa JwOYxInd5syDhadI/iZRmIzZOk4meDJbw4PL08GA0WL8jyquOOmqiYsDWwqUdBNtVh9q sgyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-transfer-encoding; bh=dpfF2HhLnCWh+A/rvJGLNLONlxYRdj17TeegRGUkPTM=; b=YmWta8/HqaDW8JJCK8HU0er7t34vOuPyi8bWuSemFcrI+SLa+RIN6CWKyboXQGo9U8 lXdP25I+aloJHu9GDQppWrZyPokXhan7nLrc3Te+uCu+joSI5tCOiPRbLhX/2mkn3viL ruTAn2D2mCGj0ewEwb4tR/92SyinyvlhRGMnIrddBgwNEfxE7KgEYmhXs2Chy2NEpf4u wcqK0Dh55YKkOCuYFjcxKm6XdvEgKQSq7MGAqEGx5kJ9ihGH7Ir31zEP+GBIeSxwei8U p8rAfU7Fa2Nxh+aA2DH4XhUsBYdrephjCnj+OJDQ5T33q1o3h6ROD/HTpG4zZNDtNEt9 XPZw== X-Gm-Message-State: APjAAAXRwEBVk2q3ohQhuvz/KsQxWlBSKyh6fHKh4kQNhmxxkyin19yw UXOUg8oyvEnWoMH+uiiBaIeUbc0iDcc= X-Google-Smtp-Source: APXvYqxhdCo7f95tfypK8EwNioSWPKxPL2DDEQkgAi/tncVIw2Q92L6XSTQd/wPlo1d5D3V0GIFPPA== X-Received: by 2002:a17:902:690b:: with SMTP id j11mr4034925plk.149.1558118807182; Fri, 17 May 2019 11:46:47 -0700 (PDT) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id d85sm13751070pfd.94.2019.05.17.11.46.46 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 17 May 2019 11:46:47 -0700 (PDT) Date: Fri, 17 May 2019 11:46:40 -0700 From: Stephen Hemminger To: dev@dpdk.org Message-ID: <20190517114640.31e1e234@hermes.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [dpdk-dev] Instability of port ids X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Several customers have reported similar issues with how the owned/stack device model works in DPDK. With failsafe/tap and VF or netvsc and VF there are DPDK ports which are marked as owned and therefore not visible. The problem is the application has to guess and workaround these port values in the port mask that gets passed in on command line. This means a working application has to modify its startup script to run on Azure. Worse the actual port values change based on the number of NIC's configured. Overall this is a nuisance for users. The whole DPDK port index concept is a bad design. In Linux/BSD there is ifindex, but few applications care, they all use names which is better. Very very few application care that eth1 is ifindex 4. The whole assignment of ports is a mess as well since it is based on probe order and that is based on PCI order, and not anything dependable. It gets worse with command line arguments, vdev, owned devices etc. All I can think of is that: * DPDK network devices need to have human readable names. current PCI is not good. * The names need to be repeatable/persistent. udev names are probably better than anything so far. Or bsd style names but they end up being device dependent. * The API to get from name to port needs to easy to use and the preferred method. * All examples and documentation should avoid using port index directly. You need port for fast rx/tx but setup should be by name.