28 Jul, 2020

3 commits

  • DAN-P (Dual Attached Nodes PRP) nodes are expected to receive
    traditional IP packets as well as PRP (Parallel Redundancy
    Protocol) tagged (trailer) packets. PRP trailer is 6 bytes
    of PRP protocol unit called RCT, Redundancy Control Trailer
    (RCT) similar to HSR tag. PRP network can have traditional
    devices such as bridges/switches or PC attached to it and
    should be able to communicate. Regular Ethernet devices treat
    the RCT as pads. This patch adds logic to format L2 frames
    from network stack to add a trailer (RCT) and send it as
    duplicates over the slave interfaces when the protocol is
    PRP as per IEC 62439-3. At the ingress, it strips the trailer,
    do duplicate detection and rejection and forward a stripped
    frame up the network stack. PRP device should accept frames
    from Singly Attached Nodes (SAN) and thus the driver mark
    the link where the frame came from in the node table.

    Signed-off-by: Murali Karicheri
    Signed-off-by: David S. Miller

    Murali Karicheri
     
  • As a preparatory patch to introduce PRP, refactor the code specific to
    handling HSR frames into separate functions and call them through
    proto_ops function pointers.

    Signed-off-by: Murali Karicheri
    Signed-off-by: David S. Miller

    Murali Karicheri
     
  • 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
    Signed-off-by: David S. Miller

    Murali Karicheri
     

07 Apr, 2019

1 commit


09 Jul, 2014

1 commit

  • This patch removes the separate paths for frames coming from the outside, and
    frames sent from the HSR device, and instead makes all frames go through
    hsr_forward_skb() in hsr_forward.c. This greatly improves code readability and
    also opens up the possibility for future support of the HSR Interlink device
    that is the basis for HSR RedBoxes and HSR QuadBoxes, as well as VLAN
    compatibility.

    Other improvements:
    * A reduction in the number of times an skb is copied on machines without
    HAVE_EFFICIENT_UNALIGNED_ACCESS, which improves throughput somewhat.
    * Headers are now created using the standard eth_header(), and using the
    standard hard_header_len.
    * Each HSR slave now gets its own private skb, so slave-specific fields can be
    correctly set.

    Signed-off-by: Arvid Brodin
    Signed-off-by: David S. Miller

    Arvid Brodin