public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: Steve Williams <steve.williams@getcruise.com>
Cc: Vladimir Oltean <olteanv@gmail.com>, netdev@vger.kernel.org
Subject: Re: [EXT] Re: [PATCH net-next] net/hanic: Add the hanic network interface for high availability links
Date: Wed, 23 Nov 2022 13:46:43 +0100	[thread overview]
Message-ID: <Y34WM8PkVvZ3Yb9y@nanopsycho> (raw)
In-Reply-To: <CALHoRjdOPdipZ8kgBCxZ_45DXiurE57YFocvgnrugGt6ugG-Dw@mail.gmail.com>

Tue, Nov 22, 2022 at 09:57:46PM CET, steve.williams@getcruise.com wrote:
>On Tue, Nov 22, 2022 at 5:55 AM Vladimir Oltean <olteanv@gmail.com> wrote:
>> Neither bond nor team have forwarding between ports built in, right?
>> Forwarding is pretty fundamental to 802.1CB (at least to the use cases
>> I know of).
>
>This driver also does not forward between ports. My intent wasn't to
>implement a bridge,
>but an endpoint. If forwarding between ports is desired, then perhaps
>you want a bridge?
>I think some other 802.1cb offerings on this list took that approach,
>but didn't seem to
>handle the endpoint case well.

Okay, could you then reply to my question asked earlier in this thread
why don't you implement this a part of bond/team instead of a new driver?

Thanks!


>
>-- 
>
>Stephen Williams
>
>Senior Software Engineer
>
>Cruise
>
>-- 
>
>
>*Confidentiality Note:* We care about protecting our proprietary 
>information, confidential material, and trade secrets. This message may 
>contain some or all of those things. Cruise will suffer material harm if 
>anyone other than the intended recipient disseminates or takes any action 
>based on this message. If you have received this message (including any 
>attachments) in error, please delete it immediately and notify the sender 
>promptly.

  reply	other threads:[~2022-11-23 13:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-18 23:26 [PATCH net-next] net/hanic: Add the hanic network interface for high availability links Steve Williams
2022-11-22  0:40 ` Andrew Lunn
2022-11-22  3:58 ` Jakub Kicinski
2022-11-22 11:34   ` Vladimir Oltean
2022-11-22 19:54     ` Andrew Lunn
2022-11-22 21:01       ` [EXT] " Steve Williams
2022-11-22 20:51     ` Steve Williams
2022-11-23 14:26       ` Vladimir Oltean
2022-11-23 14:52         ` Jiri Pirko
2022-11-23 15:12           ` Andrew Lunn
2023-02-21 11:03             ` Ferenc Fejes
2022-11-23 15:25           ` Vladimir Oltean
2022-11-23 16:36             ` Jiri Pirko
2022-11-29 22:38               ` Steve Williams
2022-11-22 12:49 ` Jiri Pirko
2022-11-22 13:55   ` Vladimir Oltean
2022-11-22 14:06     ` Jiri Pirko
2022-11-22 20:57     ` [EXT] " Steve Williams
2022-11-23 12:46       ` Jiri Pirko [this message]
2023-02-21 10:56 ` Ferenc Fejes

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=Y34WM8PkVvZ3Yb9y@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=steve.williams@getcruise.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