| commit | f3a1a3897e24370e902ec67c98bf9cdf9720a5de | [log] [tgz] |
|---|---|---|
| author | Carmelo Cascone <carmelo@opennetworking.org> | Thu Jul 27 12:04:39 2017 -0400 |
| committer | Andrea Campanella <andrea@opennetworking.org> | Fri Jul 28 15:49:56 2017 +0000 |
| tree | b39e10ad8b57934ac54eb9f23d58f45aae0fde50 | |
| parent | 482562353ade9dd1613ef9e07ccd5cfd227d4ca4 [diff] [blame] |
Removed pipeconf dependency from PiPipelineInterpreter If needed, an interpreter implementation should know which pipeconf it supports. Instead, mapping of treatments now depends on a table ID, since table in P4 can potentially support different actions with similar semantics. Change-Id: Iffbc84457f08e5dba84a8e949931849006f82535
diff --git a/drivers/bmv2/src/main/java/org/onosproject/drivers/bmv2/Bmv2PacketProgrammable.java b/drivers/bmv2/src/main/java/org/onosproject/drivers/bmv2/Bmv2PacketProgrammable.java index cbf032b..49f0f4b 100644 --- a/drivers/bmv2/src/main/java/org/onosproject/drivers/bmv2/Bmv2PacketProgrammable.java +++ b/drivers/bmv2/src/main/java/org/onosproject/drivers/bmv2/Bmv2PacketProgrammable.java
@@ -71,7 +71,7 @@ } try { - Collection<PiPacketOperation> operations = interpreter.mapOutboundPacket(packet, pipeconf); + Collection<PiPacketOperation> operations = interpreter.mapOutboundPacket(packet); operations.forEach(piPacketOperation -> { client.packetOut(piPacketOperation, pipeconf); });