public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Murali Karicheri <m-karicheri2@ti•com>
To: "open list:TI NETCP ETHERNET DRIVER" <netdev@vger•kernel.org>,
	David Miller <davem@davemloft•net>, <arvid.brodin@alten•se>
Subject: Re: Redundancy support through HSR and PRP
Date: Mon, 24 Oct 2016 12:35:32 -0400	[thread overview]
Message-ID: <580E3854.4030009@ti.com> (raw)
In-Reply-To: <5808F9FC.1080802@ti.com>

On 10/20/2016 01:08 PM, Murali Karicheri wrote:
> David,
> 
> On 10/10/2016 02:34 PM, Murali Karicheri wrote:
>> All,
>>
>> Wondering if there plan to add PRP driver support, like HSR in Linux? AFAIK, PRP
>> adds trailor to Ethernet frame and is used for Redundancy management like HSR.
>> So wondering why this is not supported.
>>
>> Thanks
>>
> I need to work on a prp driver for Linux. So if there is already someone working
> on this, I would like to join and contribute. Either way please respond so that
> I can work to add this support. 
> 
> I am also working to add support for offload HSR functions to hardware and will
> need to modify the hsr driver to support the same. So any suggestion as to how this
> can be done, will be appreciated.
> 
> Here is what I believe should happen to support this at a higher level
> 
> hsr capable NIC (with firmware support) may able to
>  - duplicate packets at the egress. So only one copy needs to be forwarded to the
>    NIC
>  - Discard the duplicate at the ingress. So forward only one to copy to the ethernet
>    driver
>  - Manage supervision of the network. Keep node list and their status
> 
> It could be a subset of the above. So I am hoping this can be published by the Ethernet
> driver as a set of features. The hsr driver can then look at this features and
> decide to offload and disable same functionality at the hsr driver. Also the node list/status
> has to be polled from the underlying hardware.
> 
> PRP is similar to HSR in many respect. Redundancy management uses a suffix tag to the MAC
> frame instead of prefix used by HSR. So they are more transparently handled by 
> switches or routers. Probably i need to do
>   - rename net/hsr to net/hsr-prp
>   - restructure the current set of files to add prp support 
> 
> Thanks
> 
+ Arvid

Didn't copy HSR owner in my original email. Copying now.


-- 
Murali Karicheri
Linux Kernel, Keystone

  reply	other threads:[~2016-10-24 16:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 18:34 Redundancy support through PRP? Murali Karicheri
2016-10-20 17:08 ` Redundancy support through HSR and PRP Murali Karicheri
2016-10-24 16:35   ` Murali Karicheri [this message]
2016-10-25 13:03     ` Arvid Brodin
     [not found]     ` <6075_1477400598_580F5816_6075_378_9_580F5825.9080109@alten.se>
2016-10-25 13:24       ` AW: " HEISE, Peter P
2016-10-27 22:54         ` Murali Karicheri

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=580E3854.4030009@ti.com \
    --to=m-karicheri2@ti$(echo .)com \
    --cc=arvid.brodin@alten$(echo .)se \
    --cc=davem@davemloft$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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