From: Vladimir Oltean <olteanv@gmail.com>
To: netdev@vger.kernel.org
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
DENG Qingfang <dqfext@gmail.com>,
Tobias Waldekranz <tobias@waldekranz.com>,
George McCollister <george.mccollister@gmail.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>,
Kurt Kanzenbach <kurt@linutronix.de>,
Marek Behun <marek.behun@nic.cz>
Subject: Re: [RFC PATCH net-next] selftests: net: dsa: add a test for ports matching on notifiers
Date: Mon, 22 Feb 2021 17:02:33 +0200 [thread overview]
Message-ID: <20210222150233.j5l5u43psfcjgbva@skbuf> (raw)
In-Reply-To: <20210222120248.1415075-1-olteanv@gmail.com>
On Mon, Feb 22, 2021 at 02:02:48PM +0200, Vladimir Oltean wrote:
> +/* CPU
> + * |
> + * sw0p0 sw0p1 sw0p2 sw0p3 sw0p4
> + * | DSA link
> + * sw1p0 sw1p1 sw1p2 sw1p3 sw1p4
> + * | DSA link
> + * sw2p0 sw2p1 sw2p2 sw2p3 sw2p4
> + */
Ha, that's one idealistic view of reality, where sw1p4 is connected to
two switches at the same time...
I'm still working on this, I'm using it to review and improve the
notifiers that we have today. I just posted it to get some comments
regarding the best way in which we should present this development tool.
Should we add all notifiers from net/dsa/switch.c or should we leave
just this "test" one, and the developer is responsible for copy-pasting
the code they want to test into this C program?
prev parent reply other threads:[~2021-02-22 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 12:02 [RFC PATCH net-next] selftests: net: dsa: add a test for ports matching on notifiers Vladimir Oltean
2021-02-22 15:02 ` Vladimir Oltean [this message]
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=20210222150233.j5l5u43psfcjgbva@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=george.mccollister@gmail.com \
--cc=horatiu.vultur@microchip.com \
--cc=kurt@linutronix.de \
--cc=marek.behun@nic.cz \
--cc=netdev@vger.kernel.org \
--cc=tobias@waldekranz.com \
--cc=vivien.didelot@gmail.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