* Preferred term for netdev master / slave
@ 2023-12-11 14:05 Donald Hunter
2023-12-12 9:57 ` Fernando F. Mancera
0 siblings, 1 reply; 3+ messages in thread
From: Donald Hunter @ 2023-12-11 14:05 UTC (permalink / raw)
To: netdev
I'm working on updates to the YNL spec for RTLINK and per
Documentation/process/coding-style I want to avoid any new use
of master / slave.
Recommended replacements include:
'{primary,main} / {secondary,replica,subordinate}'
'{initiator,requester} / {target,responder}'
'{controller,host} / {device,worker,proxy}'
Is there an existing preference for what to use in the context
of e.g. bridge master / slave?
If not, then how about one of:
primary / secondary
main / subordinate
Thanks!
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Preferred term for netdev master / slave
2023-12-11 14:05 Preferred term for netdev master / slave Donald Hunter
@ 2023-12-12 9:57 ` Fernando F. Mancera
2023-12-12 17:17 ` Stephen Hemminger
0 siblings, 1 reply; 3+ messages in thread
From: Fernando F. Mancera @ 2023-12-12 9:57 UTC (permalink / raw)
To: Donald Hunter, netdev
On 11/12/2023 15:05, Donald Hunter wrote:
> I'm working on updates to the YNL spec for RTLINK and per
> Documentation/process/coding-style I want to avoid any new use
> of master / slave.
>
> Recommended replacements include:
>
> '{primary,main} / {secondary,replica,subordinate}'
> '{initiator,requester} / {target,responder}'
> '{controller,host} / {device,worker,proxy}'
>
> Is there an existing preference for what to use in the context
> of e.g. bridge master / slave?
>
Hi Donald,
In other projects like NetworkManager, rust-netlink libraries.. the
terms that are being used in the context of linux bridging are
controller / port.
> If not, then how about one of:
>
> primary / secondary
> main / subordinate
>
> Thanks!
>
Thanks!
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: Preferred term for netdev master / slave
2023-12-12 9:57 ` Fernando F. Mancera
@ 2023-12-12 17:17 ` Stephen Hemminger
0 siblings, 0 replies; 3+ messages in thread
From: Stephen Hemminger @ 2023-12-12 17:17 UTC (permalink / raw)
To: Fernando F. Mancera; +Cc: Donald Hunter, netdev
On Tue, 12 Dec 2023 10:57:05 +0100
"Fernando F. Mancera" <ffmancera@riseup.net> wrote:
> On 11/12/2023 15:05, Donald Hunter wrote:
> > I'm working on updates to the YNL spec for RTLINK and per
> > Documentation/process/coding-style I want to avoid any new use
> > of master / slave.
> >
> > Recommended replacements include:
> >
> > '{primary,main} / {secondary,replica,subordinate}'
> > '{initiator,requester} / {target,responder}'
> > '{controller,host} / {device,worker,proxy}'
> >
> > Is there an existing preference for what to use in the context
> > of e.g. bridge master / slave?
> >
>
> Hi Donald,
>
> In other projects like NetworkManager, rust-netlink libraries.. the
> terms that are being used in the context of linux bridging are
> controller / port.
>
> > If not, then how about one of:
> >
> > primary / secondary
> > main / subordinate
> >
> > Thanks!
> >
>
> Thanks!
>
For iproute2 my intention is to replace slave with member
and not use the term master and instead refer to the interface as bridge.
Ditto for bonding.
This aligns with some other OS and implementations.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-12-12 17:17 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-12-11 14:05 Preferred term for netdev master / slave Donald Hunter
2023-12-12 9:57 ` Fernando F. Mancera
2023-12-12 17:17 ` Stephen Hemminger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).