netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Steve Williams <steve.williams@getcruise.com>
Cc: netdev@vger.kernel.org
Subject: Re: [EXT] Re: [PATCH net-next] sandlan: Add the sandlan virtual network interface
Date: Mon, 21 Nov 2022 20:02:12 -0800	[thread overview]
Message-ID: <20221121200212.77fb9a63@kernel.org> (raw)
In-Reply-To: <CALHoRjctagiFOWi8OWai5--m+sezaMHSOpKNLSQbrKEgRbs-KQ@mail.gmail.com>

On Mon, 21 Nov 2022 18:59:11 -0800 Steve Williams wrote:
> > As a general rule we don't accept any test/emulation code upstream
> > unless it comes with some tests that actually use it.
> > We have had bad experience with people adding virtual interfaces and
> > features which then bit rot or become static checker fodder and we
> > don't know whether anyone is actually using them and how.
> >
> > Is there something here that you can't achieve with appropriately
> > combined veths?  
> 
> I use the sandlan virtual interfaces to test my hanic driver, which I also just
> posted as a patch. The hanic driver implements redundant links and sets
> ethernet mac addresses, and also uses those mac addresses to infer streams
> for deduplication. The veth driver only creates pairs of nics, and it doesn't
> seem to support setting  the mac address

Understood, perhaps extending netdevsim to teach it to do packet
forwarding is an option then? I hope you'll understand that we can't
accept an extra harness driver for every protocol implementation we
accept. That is the short and the long of it.

> *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.

You absolutely _must_ get rid of this privacy notice when posting
upstream.

  reply	other threads:[~2022-11-22  4:02 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-16 22:24 [PATCH net-next] sandlan: Add the sandlan virtual network interface Steve Williams
2022-11-17  0:33 ` Andrew Lunn
2022-11-17  5:35 ` kernel test robot
2022-11-18  4:00 ` Jakub Kicinski
2022-11-22  2:59   ` [EXT] " Steve Williams
2022-11-22  4:02     ` Jakub Kicinski [this message]
2022-11-22 20:09     ` Andrew Lunn
2022-11-29 17:54       ` Steve Williams
2023-02-21 10:19         ` Ferenc Fejes
2022-11-21 14:04 ` kernel test robot

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=20221121200212.77fb9a63@kernel.org \
    --to=kuba@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).