All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tobias Waldekranz <tobias@waldekranz.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/5] net: dsa: mv88e6xxx: Improve standalone port isolation
Date: Thu, 03 Feb 2022 14:10:10 +0000	[thread overview]
Message-ID: <164389741072.16432.10654180357158986861.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220203101657.990241-1-tobias@waldekranz.com>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Thu,  3 Feb 2022 11:16:52 +0100 you wrote:
> The ideal isolation between standalone ports satisfies two properties:
> 1. Packets from one standalone port must not be forwarded to any other
>    port.
> 2. Packets from a standalone port must be sent to the CPU port.
> 
> mv88e6xxx solves (1) by isolating standalone ports using the PVT. Up
> to this point though, (2) has not guaranteed; as the ATU is still
> consulted, there is a chance that incoming packets never reach the CPU
> if its DA has previously been used as the SA of an earlier packet (see
> 1/5 for more details). This is typically not a problem, except for one
> very useful setup in which switch ports are looped in order to run the
> bridge kselftests in tools/testing/selftests/net/forwarding. This
> series attempts to solve (2).
> 
> [...]

Here is the summary with links:
  - [v2,net-next,1/5] net: dsa: mv88e6xxx: Improve isolation of standalone ports
    https://git.kernel.org/netdev/net-next/c/7af4a361a62f
  - [v2,net-next,2/5] net: dsa: mv88e6xxx: Support policy entries in the VTU
    https://git.kernel.org/netdev/net-next/c/bb03b280e0c3
  - [v2,net-next,3/5] net: dsa: mv88e6xxx: Enable port policy support on 6097
    https://git.kernel.org/netdev/net-next/c/585d42bb57bb
  - [v2,net-next,4/5] net: dsa: mv88e6xxx: Improve multichip isolation of standalone ports
    https://git.kernel.org/netdev/net-next/c/d352b20f4174
  - [v2,net-next,5/5] selftests: net: bridge: Parameterize ageing timeout
    https://git.kernel.org/netdev/net-next/c/081197591769

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-02-03 14:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 10:16 [PATCH v2 net-next 0/5] net: dsa: mv88e6xxx: Improve standalone port isolation Tobias Waldekranz
2022-02-03 10:16 ` [PATCH v2 net-next 1/5] net: dsa: mv88e6xxx: Improve isolation of standalone ports Tobias Waldekranz
2022-02-03 12:43   ` Vladimir Oltean
2022-02-03 10:16 ` [PATCH v2 net-next 2/5] net: dsa: mv88e6xxx: Support policy entries in the VTU Tobias Waldekranz
2022-02-03 10:16 ` [PATCH v2 net-next 3/5] net: dsa: mv88e6xxx: Enable port policy support on 6097 Tobias Waldekranz
2022-02-03 10:16 ` [PATCH v2 net-next 4/5] net: dsa: mv88e6xxx: Improve multichip isolation of standalone ports Tobias Waldekranz
2022-02-03 12:53   ` Vladimir Oltean
2022-02-03 10:16 ` [PATCH v2 net-next 5/5] selftests: net: bridge: Parameterize ageing timeout Tobias Waldekranz
2022-02-03 14:10 ` patchwork-bot+netdevbpf [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=164389741072.16432.10654180357158986861.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=tobias@waldekranz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.