Carmelo Cascone e5b2872eb6 Improve scalability of P4Runtime subsystem ...

The P4Runtime client was hanging (deadlock) on a master arbitration
request. As such, all other requests (e.g. table write) were waiting
for the client's request lock to become available.

Apart from fixing those deadlocks, this patch brings a number of
improvements that all together allow to run networks of 100+ P4Runtime
devices on a single ONOS instance (before only ~20 devices)

Includes:
- Asynchrounous mastership handling in DevicHandshaker (as defined in
the P4Runtime and OpenFlow spec)
- Refactored arbitration handling in the P4RuntimeClient
to be consistent with the P4Runtime spec
- Report suspect deadlocks in P4RuntimeClientImpl
- Exploit write errors in P4RuntimeClient to quickly report
channel/mastership errors to upper layers
- Complete all futures with deadlines in P4Runtime driver
- Dump all tables in one request
- Re-purposed ChannelEvent to DeviceAgentEvent to carry also mastership
response events
- Fixed IntelliJ warnings
- Various code and log clean-ups

Change-Id: I9376793a9fe69d8eddf7e8ac2ef0ee4c14fbd198

2018-06-29 13:59:27 +00:00

..

src/main/java/org/onosproject/p4runtime/api

Improve scalability of P4Runtime subsystem

2018-06-29 13:59:27 +00:00

BUCK

P4Runtime unit tests for api, ctl, model modules

2017-12-17 08:09:22 -08:00

BUILD

Add modules to Bazel build

2018-05-31 15:44:36 +00:00

pom.xml

Starting snapshot 1.14.0-SNAPSHOT

2018-04-13 12:47:31 -07:00