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 2BEC7A04A3; Tue, 16 Jun 2020 17:45:22 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9E3DE1BF8A; Tue, 16 Jun 2020 17:45:21 +0200 (CEST) Received: from mail-pf1-f179.google.com (mail-pf1-f179.google.com [209.85.210.179]) by dpdk.org (Postfix) with ESMTP id A085A1BF89 for ; Tue, 16 Jun 2020 17:45:19 +0200 (CEST) Received: by mail-pf1-f179.google.com with SMTP id h185so9695522pfg.2 for ; Tue, 16 Jun 2020 08:45:19 -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:in-reply-to:references :mime-version:content-transfer-encoding; bh=L6VJXxXBoKDdrb6wLa0nAvBZnJB0HM/yDJIG5nR/qYM=; b=O8eLTZz3q35JcuCgWG/e5+ECAB+S1GUK3iJkNcbPmVPWzDEkejxu78OeFUWpkdZrKH 30OCr++B/BGfRTkTqc2JvaIfdYN+lxIlA42LvZV5BEiTrDhxp0Dzb24MXLY33V4A7TzS bKrQyO7lj3qvYWzv/6XM79Srlwig3RdURC54DSsfNEf7x5YeBjNL5uWiz7/+Z9TOBdnr dR/dyOuXpCj9rO9JDK2RDFHfCMc3pkGdiVhhu1BQe06MefvHuzcLOJAmkd4Hnu72jnkl HfNBreCdYYbIfSDSuP+kdkDKKUwbDXnYgmuOF0voL8mMk7OVVGDCfFXN9/BrMjb9mGO8 twqw== 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=L6VJXxXBoKDdrb6wLa0nAvBZnJB0HM/yDJIG5nR/qYM=; b=UQvDUGOTXxxynVvG9XnCfMg8RMg4zBrlWnaH/alrOlW817pyJ01zVEBHnd7A9q5aRU w9l05Pm7jrBBCe+WuXM4U+Jo2UfBc7h1d1FJEjJDxKUPVbyKNTfuPbfRLJuqFRvh0t1D m5AYuyNBtEfIYr4SF+y3PxEgt1PqpDaSez6YykdtzeRtfIFkj4UV6omEmW3tDGmfcKg4 2fSYFTllyfK7JmEYu0+X0YdRCgZ83MLQsflPPWrEGbL8AljJewbvmlqj3U9ESQR4i5x8 BjU4lLjP9Zaw29+Ru/M60q0vs91c10APLOWqSRozxBguzfUWcxG5jRJFtO6n14diAPZX 5iDw== X-Gm-Message-State: AOAM53013cLjD4KvrpAy46/eiBI8wWA31o/gFWgaCFmVvCiOCMmcbhoD dwB8vwaie9VkZzOdolzu1B1s8A== X-Google-Smtp-Source: ABdhPJwia5OBzTd5JxP3O1e3Sx/n3eNsHFLPvMf5CEz01AYdY6qNXNSSiAUSU71KL/NYxIxXUQDhRg== X-Received: by 2002:a62:8c12:: with SMTP id m18mr2686024pfd.111.1592322318498; Tue, 16 Jun 2020 08:45:18 -0700 (PDT) Received: from hermes.lan (204-195-22-127.wavecable.com. [204.195.22.127]) by smtp.gmail.com with ESMTPSA id a17sm17422481pfi.203.2020.06.16.08.45.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 16 Jun 2020 08:45:18 -0700 (PDT) Date: Tue, 16 Jun 2020 08:45:09 -0700 From: Stephen Hemminger To: Chas Williams <3chas3@gmail.com> Cc: dev@dpdk.org Message-ID: <20200616084509.2810b5d4@hermes.lan> In-Reply-To: References: <20200615155237.682a89af@hermes.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [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" On Tue, 16 Jun 2020 09:52:01 -0400 Chas Williams <3chas3@gmail.com> wrote: > On 6/16/20 7:48 AM, Jay Rolette wrote: > > On Mon, Jun 15, 2020 at 5:52 PM Stephen Hemminger < > > stephen@networkplumber.org> wrote: > > > >> 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. > >> > > > > LACP is only 1 of 5 bonding modes. > > > > > >> 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. > >> > > > > Why rename rte_eth_bond at all? > > If there is a strong desire to rename the PMD, I suggest using link > aggregration group (LAG/lag) since that is a more accurate description of > this feature. That's the terminology used in 802.1AX. This would make > some of the internal name changes more natural as well. The words that matter most are getting rid of master/slave and blacklist/whitelist. The worst is "bonded slave". Luckily the master and slave are only used internally in the driver so no visible API/ABI with those terms. One option would be to substitute slave with multiplexer in the comments and shorter term like mux in the variables. And replace master with aggregator. You are right, the standard name is LACP other names seem to be viewed as early history alternatives: Cisco - Etherchannel Juniper - Aggregated Ethernet Others - Multi-link BSD - lagg Linux bonding Solaris aggr The point of this thread is to get consensus about best future naming.