On 6/16/20 7:48 AM, Jay Rolette wrote:
> On Mon, Jun 15, 2020 at 5:52 PM Stephen Hemminger <
> step...@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.
>
>
>> 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.
>>
>
> The current naming appears to be a straight copy of the Linux naming + a
> prefix change.
>
