~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

TOMOYO Linux Cross Reference
Linux/net/hsr/Kconfig

Version: ~ [ linux-6.12-rc7 ] ~ [ linux-6.11.7 ] ~ [ linux-6.10.14 ] ~ [ linux-6.9.12 ] ~ [ linux-6.8.12 ] ~ [ linux-6.7.12 ] ~ [ linux-6.6.60 ] ~ [ linux-6.5.13 ] ~ [ linux-6.4.16 ] ~ [ linux-6.3.13 ] ~ [ linux-6.2.16 ] ~ [ linux-6.1.116 ] ~ [ linux-6.0.19 ] ~ [ linux-5.19.17 ] ~ [ linux-5.18.19 ] ~ [ linux-5.17.15 ] ~ [ linux-5.16.20 ] ~ [ linux-5.15.171 ] ~ [ linux-5.14.21 ] ~ [ linux-5.13.19 ] ~ [ linux-5.12.19 ] ~ [ linux-5.11.22 ] ~ [ linux-5.10.229 ] ~ [ linux-5.9.16 ] ~ [ linux-5.8.18 ] ~ [ linux-5.7.19 ] ~ [ linux-5.6.19 ] ~ [ linux-5.5.19 ] ~ [ linux-5.4.285 ] ~ [ linux-5.3.18 ] ~ [ linux-5.2.21 ] ~ [ linux-5.1.21 ] ~ [ linux-5.0.21 ] ~ [ linux-4.20.17 ] ~ [ linux-4.19.323 ] ~ [ linux-4.18.20 ] ~ [ linux-4.17.19 ] ~ [ linux-4.16.18 ] ~ [ linux-4.15.18 ] ~ [ linux-4.14.336 ] ~ [ linux-4.13.16 ] ~ [ linux-4.12.14 ] ~ [ linux-4.11.12 ] ~ [ linux-4.10.17 ] ~ [ linux-4.9.337 ] ~ [ linux-4.4.302 ] ~ [ linux-3.10.108 ] ~ [ linux-2.6.32.71 ] ~ [ linux-2.6.0 ] ~ [ linux-2.4.37.11 ] ~ [ unix-v6-master ] ~ [ ccs-tools-1.8.12 ] ~ [ policy-sample ] ~
Architecture: ~ [ i386 ] ~ [ alpha ] ~ [ m68k ] ~ [ mips ] ~ [ ppc ] ~ [ sparc ] ~ [ sparc64 ] ~

  1 # SPDX-License-Identifier: GPL-2.0-only
  2 #
  3 # IEC 62439-3 High-availability Seamless Redundancy
  4 #
  5 
  6 config HSR
  7         tristate "High-availability Seamless Redundancy (HSR & PRP)"
  8         help
  9           This enables IEC 62439 defined High-availability Seamless
 10           Redundancy (HSR) and Parallel Redundancy Protocol (PRP).
 11 
 12           If you say Y here, then your Linux box will be able to act as a
 13           DANH ("Doubly attached node implementing HSR") or DANP ("Doubly
 14           attached node implementing PRP"). For this to work, your Linux box
 15           needs (at least) two physical Ethernet interfaces.
 16 
 17           For DANH, it must be connected as a node in a ring network together
 18           with other HSR capable nodes. All Ethernet frames sent over the HSR
 19           device will be sent in both directions on the ring (over both slave
 20           ports), giving a redundant, instant fail-over network. Each HSR node
 21           in the ring acts like a bridge for HSR frames, but filters frames
 22           that have been forwarded earlier.
 23 
 24           For DANP, it must be connected as a node connecting to two
 25           separate networks over the two slave interfaces. Like HSR, Ethernet
 26           frames sent over the PRP device will be sent to both networks giving
 27           a redundant, instant fail-over network. Unlike HSR, PRP networks
 28           can have Singly Attached Nodes (SAN) such as PC, printer, bridges
 29           etc and will be able to communicate with DANP nodes.
 30 
 31           This code is a "best effort" to comply with the HSR standard as
 32           described in IEC 62439-3:2010 (HSRv0) and IEC 62439-3:2012 (HSRv1),
 33           and PRP standard described in IEC 62439-4:2012 (PRP), but no
 34           compliancy tests have been made. Use iproute2 to select the protocol
 35           you would like to use.
 36 
 37           You need to perform any and all necessary tests yourself before
 38           relying on this code in a safety critical system!
 39 
 40           If unsure, say N.

~ [ source navigation ] ~ [ diff markup ] ~ [ identifier search ] ~

kernel.org | git.kernel.org | LWN.net | Project Home | SVN repository | Mail admin

Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.

sflogo.php