From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f195.google.com (mail-pf1-f195.google.com [209.85.210.195]) by dpdk.org (Postfix) with ESMTP id 70E9A4C8D for ; Mon, 4 Mar 2019 20:14:08 +0100 (CET) Received: by mail-pf1-f195.google.com with SMTP id u9so3701038pfn.1 for ; Mon, 04 Mar 2019 11:14:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=x5mFit4vHRl5ZdAf3XAMGfxuXmfIBLOu6XtyE7ueIL4=; b=dmUKe9TNc35dj+c2vlrjFBwUQifPz+81ogvO849vHqK0K4FjA4tg2eStLSTKtsC7UJ io6Q9tnE9KlerWnQFuPm0I2LEJp4UHpcUC+jP/IKTtw7z1FkJqkrfpk0Sb8b3sgKJfxA 2ZSKTa0HMAf3C0WClw/CU/78TraaqWU+YIGeJYRL0pFeDpwvfp3YMK/WCcu00baOR9jO OJfGp0mpcT7Yp6Xn0/27j2h7dyfO1tQ6nVGzwH0ULmFG5fnOfLX6v5CFFoFmWM5ImRkX Sv8pfShIMQnQf7JzEIDOUonHj4P3DratGUd99Xb36AZwHx1KKmXfzoVEJoqX5dIYquBR QjnQ== 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:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=x5mFit4vHRl5ZdAf3XAMGfxuXmfIBLOu6XtyE7ueIL4=; b=sQ987oUOJrTgAsqldsk3JOYBJeBZ0J643QHATPvDw3fxj4bGswWWc1Qt0FKVXr4IMY 9p8b8lOf2xW5ULOPnZGcSIBesydpJXXhnvWx3x0ywUcpXLxgojLt4NhOSwS2Fqo+HhvT IGml4w/TnADwyuzV9oTWJ/G5pVWdQoHyTTBBU5qIfSKiUJqe5KWkZNDyLJ8+FNn5O9Ua OqN9weziYGMQnCBuRtwMY1wxiAtzZ/PIQG9i69xYJ/d3pgXBFIkv13HqAdW6c9OHsjdw czSaAUnInytNhQ/vsIGWYykKyrxNxWypvJkQYjNX0gEhFLjBv7Vt2h114eG4jcTxNYei Ac3g== X-Gm-Message-State: AHQUAuaffAGGzK+4XAD6KUK8Ag5NiLnFMMrcKcnJgK08H5vwbVLugtPi EzYmg9ySKoLIcaAwYKJlb5w/CQaOAnk= X-Google-Smtp-Source: APXvYqwTNvEMZXYF8r+gmCTcJ1IjufZCBpLGzi1uqnGJiPudSBy0AZ7JgnTso7SZbr2J6w+MI2bWsg== X-Received: by 2002:a62:4389:: with SMTP id l9mr22208607pfi.170.1551726847469; Mon, 04 Mar 2019 11:14:07 -0800 (PST) Received: from shemminger-XPS-13-9360 ([167.220.104.59]) by smtp.gmail.com with ESMTPSA id f192sm12114574pfc.180.2019.03.04.11.14.07 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 04 Mar 2019 11:14:07 -0800 (PST) Date: Mon, 4 Mar 2019 11:14:04 -0800 From: Stephen Hemminger To: Dekel Peled Cc: Shahaf Shuler , Yongseok Koh , "dev@dpdk.org" , Ori Kam , Matan Azrad Message-ID: <20190304111404.0225aa46@shemminger-XPS-13-9360> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [RFC v2] net/mlx5: support new naming scheme for representors 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: , X-List-Received-Date: Mon, 04 Mar 2019 19:14:08 -0000 On Sun, 3 Mar 2019 07:14:07 +0000 Dekel Peled wrote: > In current kernel implementation, the physical port name for representors is a numeric string (i.e. '0', '1', etc.). > > > > Kernel patch [1] implements an updated scheme for naming of representors ports. > > The new scheme gives a unique name for each port using the PF ID and the VF ID. > > Uplink representors are named 'p0', 'p1', etc. > > VF representors are named 'pf0vf0', 'pf0vf1', 'pf1vf0', 'pf1vf1', etc. Depending on kernel to use any particular naming policy is going to be problematic. Users will want to run on older kernels, and many distributions rename interfaces through udev or other mechanism.