All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hangbin Liu <liuhangbin@gmail.com>
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: bridge@lists.linux-foundation.org,
	Ido Schimmel <idosch@nvidia.com>, Roopa Prabhu <roopa@nvidia.com>,
	Jakub Kicinski <kuba@kernel.org>,
	netdev@vger.kernel.org
Subject: Re: [Bridge] [Question] Any plan to write/update the bridge doc?
Date: Thu, 27 Apr 2023 11:38:06 +0800	[thread overview]
Message-ID: <ZEnuHppYIE3bCxEs@Laptop-X1> (raw)
In-Reply-To: <5ddac447-c268-e559-a8dc-08ae3d124352@blackwall.org>

On Tue, Apr 25, 2023 at 11:04:47AM +0300, Nikolay Aleksandrov wrote:
> Always +1 for keeping the man pages up-to-date, but I tend to agree with Jakub as well
> that it'd be nice to have an in-kernel doc which explains the uapi and potentially
> at least some more obscure internals (if not all), we can insist on updating it
> for new changes
> 
> I'd be happy to help fill such doc, but at the moment I don't have the
> time to write the basis for it. As Hangbin nicely offered, I think we can start
> there. For a start it'd be nice to make an initial outline of the different sections
> and go on filling them from there.
> 
> E.g. as a starter something like (feel free to edit):
> Introduction
> Bridge internals (fdb, timers, MTU handling, fwding decisions, ports, synchronization)
> STP (mst, rstp, timers, user-space stp etc)
> Multicast (mdb, igmp, eht, vlan-mcast etc)
> VLAN (filtering, options, tunnel...)
> Switchdev
> Netfilter
> MRP/CFM (?)
> FAQ
> 
> Each of these having uapi sections with descriptions. We can include references
> to the iproute2 docs for cmd explanations and examples, but in this doc we'll have
> the uapi descriptions and maybe some helpful information about internal implementation
> that would save future contributors time.
> 
> At the very least we can do the uapi part for each section so options are described
> and uapi nl attribute structures are explained.

OK, I will try start a draft version after the Labor holiday.

Hangbin

WARNING: multiple messages have this Message-ID (diff)
From: Hangbin Liu <liuhangbin@gmail.com>
To: Nikolay Aleksandrov <razor@blackwall.org>
Cc: Ido Schimmel <idosch@nvidia.com>,
	netdev@vger.kernel.org, Roopa Prabhu <roopa@nvidia.com>,
	bridge@lists.linux-foundation.org,
	Jakub Kicinski <kuba@kernel.org>
Subject: Re: [Question] Any plan to write/update the bridge doc?
Date: Thu, 27 Apr 2023 11:38:06 +0800	[thread overview]
Message-ID: <ZEnuHppYIE3bCxEs@Laptop-X1> (raw)
In-Reply-To: <5ddac447-c268-e559-a8dc-08ae3d124352@blackwall.org>

On Tue, Apr 25, 2023 at 11:04:47AM +0300, Nikolay Aleksandrov wrote:
> Always +1 for keeping the man pages up-to-date, but I tend to agree with Jakub as well
> that it'd be nice to have an in-kernel doc which explains the uapi and potentially
> at least some more obscure internals (if not all), we can insist on updating it
> for new changes
> 
> I'd be happy to help fill such doc, but at the moment I don't have the
> time to write the basis for it. As Hangbin nicely offered, I think we can start
> there. For a start it'd be nice to make an initial outline of the different sections
> and go on filling them from there.
> 
> E.g. as a starter something like (feel free to edit):
> Introduction
> Bridge internals (fdb, timers, MTU handling, fwding decisions, ports, synchronization)
> STP (mst, rstp, timers, user-space stp etc)
> Multicast (mdb, igmp, eht, vlan-mcast etc)
> VLAN (filtering, options, tunnel...)
> Switchdev
> Netfilter
> MRP/CFM (?)
> FAQ
> 
> Each of these having uapi sections with descriptions. We can include references
> to the iproute2 docs for cmd explanations and examples, but in this doc we'll have
> the uapi descriptions and maybe some helpful information about internal implementation
> that would save future contributors time.
> 
> At the very least we can do the uapi part for each section so options are described
> and uapi nl attribute structures are explained.

OK, I will try start a draft version after the Labor holiday.

Hangbin

  reply	other threads:[~2023-04-27  3:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24  9:25 [Bridge] [Question] Any plan to write/update the bridge doc? Hangbin Liu
2023-04-24  9:25 ` Hangbin Liu
2023-04-24 15:46 ` [Bridge] " Ido Schimmel
2023-04-24 15:46   ` Ido Schimmel
2023-04-24 15:59   ` [Bridge] " Stephen Hemminger
2023-04-24 15:59     ` Stephen Hemminger
2023-04-25  8:04   ` [Bridge] " Nikolay Aleksandrov
2023-04-25  8:04     ` Nikolay Aleksandrov
2023-04-27  3:38     ` Hangbin Liu [this message]
2023-04-27  3:38       ` Hangbin Liu
2023-04-24 21:28 ` [Bridge] " Jakub Kicinski
2023-04-24 21:28   ` Jakub Kicinski
2023-04-24 22:08   ` [Bridge] " Stephen Hemminger
2023-04-24 22:08     ` Stephen Hemminger
2023-04-25  3:58   ` Hangbin Liu
2023-04-25  3:58     ` Hangbin Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZEnuHppYIE3bCxEs@Laptop-X1 \
    --to=liuhangbin@gmail.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=razor@blackwall.org \
    --cc=roopa@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.