From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: netdev@vger.kernel.org, Florian Fainelli <f.fainelli@gmail.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
Jiri Pirko <jiri@resnulli.us>, Ido Schimmel <idosch@idosch.org>,
DENG Qingfang <dqfext@gmail.com>,
Tobias Waldekranz <tobias@waldekranz.com>,
George McCollister <george.mccollister@gmail.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Kurt Kanzenbach <kurt@linutronix.de>
Subject: Re: [RFC PATCH net-next 10/12] Documentation: networking: dsa: add paragraph for the HSR/PRP offload
Date: Thu, 25 Feb 2021 02:42:04 +0100 [thread overview]
Message-ID: <YDcAbFkT+OkE70kh@lunn.ch> (raw)
In-Reply-To: <20210221213355.1241450-11-olteanv@gmail.com>
> +IEC 62439-3 (HSR/PRP)
> +---------------------
> +
> +The Parallel Redundancy Protocol (PRP) is a network redundancy protocol which
> +works by duplicating and sequence numbering packets through two independent L2
> +networks (which are unaware of the PRP tail tags carried in the packets), and
> +eliminating the duplicates at the receiver. The High-availability Seamless
> +Redundancy (HSR) protocol is similar in concept, except all nodes that carry
> +the redundant traffic are aware of the fact that it is HSR-tagged (because HSR
> +uses a header with an EtherType of 0x892f) and are physically connected in a
> +ring topology. Both HSR and PRP use supervision frames for monitoring the
I don't know HSR/PRP terms. Should it be supervisory instead of
supervision?
> +health of the network and for discovering the other nodes.
Either "discovering other nodes" or "discovery of other nodes".
> +
> +In Linux, both HSR and PRP are implemented in the hsr driver, which
> +instantiates a virtual, stackable network interface with two member ports.
> +The driver only implements the basic roles of DANH (Doubly Attached Node
> +implementing HSR) and DANP (Doubly Attached Node implementing PRP); the roles
> +of RedBox and QuadBox aren't (therefore, bridging a hsr network interface with
In colloquial English, you can get away with just 'aren't'. But in
Queens English, you should follow it with something, in this case
'supported'.
Andrew
next prev parent reply other threads:[~2021-02-25 1:42 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 21:33 [RFC PATCH net-next 00/12] Documentation updates for switchdev and DSA Vladimir Oltean
2021-02-21 21:33 ` [RFC PATCH net-next 01/12] Documentation: networking: update the graphical representation Vladimir Oltean
2021-02-22 5:06 ` Florian Fainelli
2021-02-25 19:29 ` Tobias Waldekranz
2021-02-21 21:33 ` [RFC PATCH net-next 02/12] Documentation: networking: dsa: rewrite chapter about tagging protocol Vladimir Oltean
2021-02-22 5:12 ` Florian Fainelli
2021-02-24 23:54 ` Andrew Lunn
2021-02-25 20:29 ` Tobias Waldekranz
2021-02-26 18:12 ` Vladimir Oltean
2021-02-26 23:19 ` Tobias Waldekranz
2021-02-21 21:33 ` [RFC PATCH net-next 03/12] Documentation: networking: dsa: remove static port count from limitations Vladimir Oltean
2021-02-22 5:13 ` Florian Fainelli
2021-02-21 21:33 ` [RFC PATCH net-next 04/12] Documentation: networking: dsa: remove references to switchdev prepare/commit Vladimir Oltean
2021-02-22 5:13 ` Florian Fainelli
2021-02-24 23:57 ` Andrew Lunn
2021-02-21 21:33 ` [RFC PATCH net-next 05/12] Documentation: networking: dsa: remove TODO about porting more vendor drivers Vladimir Oltean
2021-02-22 5:14 ` Florian Fainelli
2021-02-24 23:59 ` Andrew Lunn
2021-02-21 21:33 ` [RFC PATCH net-next 06/12] Documentation: networking: dsa: document the port_bridge_flags method Vladimir Oltean
2021-02-22 5:15 ` Florian Fainelli
2021-02-25 1:14 ` Andrew Lunn
2021-02-21 21:33 ` [RFC PATCH net-next 07/12] Documentation: networking: dsa: mention integration with devlink Vladimir Oltean
2021-02-22 5:16 ` Florian Fainelli
2021-02-25 1:20 ` Andrew Lunn
2021-02-21 21:33 ` [RFC PATCH net-next 08/12] Documentation: networking: dsa: add paragraph for the LAG offload Vladimir Oltean
2021-02-22 5:18 ` Florian Fainelli
2021-02-25 1:27 ` Andrew Lunn
2021-02-25 20:42 ` Tobias Waldekranz
2021-02-26 18:09 ` Vladimir Oltean
2021-02-21 21:33 ` [RFC PATCH net-next 09/12] Documentation: networking: dsa: add paragraph for the MRP offload Vladimir Oltean
2021-02-22 5:19 ` Florian Fainelli
2021-02-22 19:46 ` Horatiu Vultur
2021-02-22 20:25 ` Vladimir Oltean
2021-02-23 13:30 ` Horatiu Vultur
2021-02-23 13:50 ` Vladimir Oltean
2021-02-23 14:18 ` Horatiu Vultur
2021-02-25 1:32 ` Andrew Lunn
2021-02-21 21:33 ` [RFC PATCH net-next 10/12] Documentation: networking: dsa: add paragraph for the HSR/PRP offload Vladimir Oltean
2021-02-22 5:21 ` Florian Fainelli
2021-02-22 14:48 ` George McCollister
2021-02-25 1:42 ` Andrew Lunn [this message]
2021-02-25 13:33 ` George McCollister
2021-02-21 21:33 ` [RFC PATCH net-next 11/12] Documentation: networking: switchdev: clarify device driver behavior Vladimir Oltean
2021-02-25 1:57 ` Andrew Lunn
2021-02-28 16:11 ` Ido Schimmel
2021-02-21 21:33 ` [RFC PATCH net-next 12/12] Documentation: networking: switchdev: fix command for static FDB entries Vladimir Oltean
2021-02-22 5:24 ` Florian Fainelli
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=YDcAbFkT+OkE70kh@lunn.ch \
--to=andrew@lunn.ch \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=idosch@idosch.org \
--cc=jiri@resnulli.us \
--cc=kurt@linutronix.de \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=tobias@waldekranz.com \
--cc=vivien.didelot@gmail.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 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).