mirror of
https://github.com/AuxXxilium/linux_dsm_epyc7002.git
synced 2024-12-28 11:18:45 +07:00
8f4c0e0178
Parallel Redundancy Protocol (PRP) is another redundancy protocol introduced by IEC 63439 standard. It is similar to HSR in many aspects:- - Use a pair of Ethernet interfaces to created the PRP device - Use a 6 byte redundancy protocol part (RCT, Redundancy Check Trailer) similar to HSR Tag. - Has Link Redundancy Entity (LRE) that works with RCT to implement redundancy. Key difference is that the protocol unit is a trailer instead of a prefix as in HSR. That makes it inter-operable with tradition network components such as bridges/switches which treat it as pad bytes, whereas HSR nodes requires some kind of translators (Called redbox) to talk to regular network devices. This features allows regular linux box to be converted to a DAN-P box. DAN-P stands for Dual Attached Node - PRP similar to DAN-H (Dual Attached Node - HSR). Add a comment at the header/source code to explicitly state that the driver files also handles PRP protocol as well. Signed-off-by: Murali Karicheri <m-karicheri2@ti.com> Signed-off-by: David S. Miller <davem@davemloft.net>
41 lines
1.7 KiB
Plaintext
41 lines
1.7 KiB
Plaintext
# SPDX-License-Identifier: GPL-2.0-only
|
|
#
|
|
# IEC 62439-3 High-availability Seamless Redundancy
|
|
#
|
|
|
|
config HSR
|
|
tristate "High-availability Seamless Redundancy (HSR & PRP)"
|
|
help
|
|
This enables IEC 62439 defined High-availability Seamless
|
|
Redundancy (HSR) and Parallel Redundancy Protocol (PRP).
|
|
|
|
If you say Y here, then your Linux box will be able to act as a
|
|
DANH ("Doubly attached node implementing HSR") or DANP ("Doubly
|
|
attached node implementing PRP"). For this to work, your Linux box
|
|
needs (at least) two physical Ethernet interfaces.
|
|
|
|
For DANH, it must be connected as a node in a ring network together
|
|
with other HSR capable nodes. All Ethernet frames sent over the HSR
|
|
device will be sent in both directions on the ring (over both slave
|
|
ports), giving a redundant, instant fail-over network. Each HSR node
|
|
in the ring acts like a bridge for HSR frames, but filters frames
|
|
that have been forwarded earlier.
|
|
|
|
For DANP, it must be connected as a node connecting to two
|
|
separate networks over the two slave interfaces. Like HSR, Ethernet
|
|
frames sent over the PRP device will be sent to both networks giving
|
|
a redundant, instant fail-over network. Unlike HSR, PRP networks
|
|
can have Singly Attached Nodes (SAN) such as PC, printer, bridges
|
|
etc and will be able to communicate with DANP nodes.
|
|
|
|
This code is a "best effort" to comply with the HSR standard as
|
|
described in IEC 62439-3:2010 (HSRv0) and IEC 62439-3:2012 (HSRv1),
|
|
and PRP standard described in IEC 62439-4:2012 (PRP), but no
|
|
compliancy tests have been made. Use iproute2 to select the protocol
|
|
you would like to use.
|
|
|
|
You need to perform any and all necessary tests yourself before
|
|
relying on this code in a safety critical system!
|
|
|
|
If unsure, say N.
|