From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 33F04A04A3; Tue, 16 Jun 2020 00:52:49 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0F88F2B94; Tue, 16 Jun 2020 00:52:48 +0200 (CEST) Received: from mail-pj1-f51.google.com (mail-pj1-f51.google.com [209.85.216.51]) by dpdk.org (Postfix) with ESMTP id 398EBFFA for ; Tue, 16 Jun 2020 00:52:47 +0200 (CEST) Received: by mail-pj1-f51.google.com with SMTP id d6so582671pjs.3 for ; Mon, 15 Jun 2020 15:52:46 -0700 (PDT) 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:mime-version :content-transfer-encoding; bh=gdK1H2zZ4WTQpVuttcgSgTOs+k2+X8e6fFkUqmsTPvU=; b=tU966pBztf5mgObvROXC/3CH8iIc10JPdKeoe2eb2SlW7oFK/hJZ+bIMQNoASD2uSK QyknTQPhH3DnVQjumfBxFgVqeJTH5LmNqoLvLffEEtkkpD0642Z+07p9KSZeE7KvlX+9 YRIF6l3mSsHTbKY1j7OxYiQ0oKofH9urL26hKycRqHPH69JBucyLDU4npLvFzwl1Vrwa EApI8l+go8T2kzZcTQnkVI6fkmae04aRERpezmoj4oTy7MOLJ5atfW63g4q7Ft6nR3Hb ut1uhUOGkEjMHNUJ5NhB2EFOCSeBzrBTzlw47aByUIebULDdccnf5AhJv8L0rkscXUbl mJ8A== 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:mime-version :content-transfer-encoding; bh=gdK1H2zZ4WTQpVuttcgSgTOs+k2+X8e6fFkUqmsTPvU=; b=Nfu7YaKGNxWYN9hSCThPvJKmGX5uASQJEaRBd5ktEy1Z3H5nylOafhsIDYxeym9o4/ vwvA9I+/Pyc8WJ1y/n8UflmxT4cY+ut6euw9xHopgdL1Nl7A+cHxXL46PIndYZDjN9Ug rYKOyx0/NWMsBpxqHKhCQYJC/eYHHQ0VPzqG8Bx+dos03E50LCVk6RJaZfYwfbKAXAKb iyPkSaapDaBqae91a4fIIVy9KH9O+xTw+t7kpCshtPUzkJGoPd0LA7+T3ZIRQVjs7ID5 8/0zO7qTgZDiz7aLstjS5BTCoSN2KeXGXZppLS3/5/6n9Z5yifgHUh5UxzAEMAxWGNpL CyNg== X-Gm-Message-State: AOAM531Mkzejw6tXxAjjO5ITVVqA0E6kep5OFOWfRzSryfgBZeT0Jc11 doOkB+3/KweOzrw+SDJl/p8kXA== X-Google-Smtp-Source: ABdhPJzEAT+SDTCPaZYGH1EPCyK6q6RUftH9utl8M3ZBZ6lnXUtbmFoop1cAEc0tGdekduKoj+hrog== X-Received: by 2002:a17:90a:1781:: with SMTP id q1mr202793pja.8.1592261566184; Mon, 15 Jun 2020 15:52:46 -0700 (PDT) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id z11sm15202998pfk.141.2020.06.15.15.52.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 15 Jun 2020 15:52:45 -0700 (PDT) Date: Mon, 15 Jun 2020 15:52:37 -0700 From: Stephen Hemminger To: Chas Williams , "Wei Hu (Xavier)" Cc: dev@dpdk.org Message-ID: <20200615155237.682a89af@hermes.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [dpdk-dev] Aligning DPDK Link bonding with current standards terminology 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" I am disturbed by the wide spread use of master/slave in Ethernet bonding. Asked the current IEEE chairs and it looks like it is already fixed "upstream". The proper terminology is for Ethernet link aggregation in the the current standard 802.1AX 2020 revision (pay walled) for the parts formerly known as master and slave is now "Protocol Parser" and "Protocol multiplexer". Also it is not called bonding anywhere; it uses LACP only. Given the large scope of the name changes. Maybe it would be best to just convert the names all of rte_eth_bond to rte_eth_lacp and fix the master/slave references at the same time. For one brief release (20.08) keep both drivers and mark the bond on as deprecated. It would also help if all the documentation and tests were checked to see if they align with the current standard.