On 4/3/17, 2:40 AM, "[email protected] on behalf of Matthias May"
<[email protected] on behalf of [email protected]> wrote:
When using openvswitch in combination with a hardware switch attached via
dsa
it may be desirable to prevent frames from being looped back to interfaces
which reside on the same switch and are already processed by the
switching fabric in hardware.
This patch series achieves this by introducing a new parameter port_group to
be used by the normal action.
When the port_group is not set explicitly, it defaults to the ofp number.
Ports which are in the same group will not forward a frame between each
other.
This looks like port isolation to me – how about something wild and crazy like
“isolation ID”.
The “group” part may even be considered misleading and unfortunately is used
in other different networking contexts.
Matthias May (6):
port_group: add db definitions
port_group: add documentation entry
port_group: bridge: set port_group in port config
port_group: ofproto: add port_group definition
port_group: ofproto-dpif: add port_group definition and init
port_group: ofproto-dpif-xlate: implement port_group
ofproto/ofproto-dpif-xlate.c | 53
+++++++++++++++++++++++++++++++++-----------
ofproto/ofproto-dpif-xlate.h | 4 ++--
ofproto/ofproto-dpif.c | 13 +++++++++--
ofproto/ofproto.h | 1 +
vswitchd/bridge.c | 11 +++++++++
vswitchd/vswitch.ovsschema | 9 ++++++--
vswitchd/vswitch.xml | 7 ++++++
7 files changed, 79 insertions(+), 19 deletions(-)
--
2.11.0
_______________________________________________
dev mailing list
[email protected]
https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddev&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=BVhFA09CGX7JQ5Ih-uZnsw&m=ElDHweksMtkAyJMxLsPjY2CvtmkRMpGeiCOq1tmSc6E&s=O7RObYM603xAIAfqioZQQyjLACrZ-3tM0KOeot5Xjik&e=
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
