From: Jiri Pirko <jiri@resnulli.us>
To: Steve Williams <steve.williams@getcruise.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net/hanic: Add the hanic network interface for high availability links
Date: Tue, 22 Nov 2022 13:49:38 +0100 [thread overview]
Message-ID: <Y3zFYh55h7y/TQXB@nanopsycho> (raw)
In-Reply-To: <20221118232639.13743-1-steve.williams@getcruise.com>
Sat, Nov 19, 2022 at 12:26:39AM CET, steve.williams@getcruise.com wrote:
>This is a virtual device that implements support for 802.1cb R-TAGS
>and duplication and deduplication. The hanic nic itself is not a device,
>but enlists ethernet nics to act as parties in a high-availability
>link. Outbound packets are duplicated and tagged with R-TAGs, then
>set out the enlisted links. Inbound packets with R-TAGs have their
>R-TAGs removed, and duplicates are dropped to complete the link. The
>algorithm handles links being completely disconnected, sporadic packet
>loss, and out-of-order arrivals.
>
>To the extent possible, the link is self-configuring: It detects and
>brings up streams as R-TAG'ed packets are detected, and creates streams
>for outbound packets unless explicitly filtered to skip tagging.
>---
> Documentation/networking/hanic.rst | 351 ++++++++++
> Documentation/networking/index.rst | 1 +
> MAINTAINERS | 6 +
> drivers/net/Kconfig | 17 +
> drivers/net/Makefile | 1 +
> drivers/net/hanic/Makefile | 15 +
> drivers/net/hanic/hanic_dev.c | 1006 ++++++++++++++++++++++++++++
> drivers/net/hanic/hanic_filter.c | 172 +++++
> drivers/net/hanic/hanic_main.c | 109 +++
> drivers/net/hanic/hanic_netns.c | 58 ++
> drivers/net/hanic/hanic_priv.h | 408 +++++++++++
> drivers/net/hanic/hanic_protocol.c | 350 ++++++++++
> drivers/net/hanic/hanic_streams.c | 161 +++++
> drivers/net/hanic/hanic_sysfs.c | 672 +++++++++++++++++++
> 14 files changed, 3327 insertions(+)
Leaving aside issues I spotted looking at random parts of the code (like
checking if kernel version is >5 :O), why this has to be another
master-slave device? From the first look, I think this could be
implemented as a bond/team mode. You would save a lot of plumbing code
and ease up the maintainance burden. Did you consider that option?
Any particular arguments against that approach?
Thanks!
next prev parent reply other threads:[~2022-11-22 12:49 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 [this message]
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
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=Y3zFYh55h7y/TQXB@nanopsycho \
--to=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--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