Added an UNORDERED option to QueueKeeper 36/3736/3
authorEd Warnicke <eaw@cisco.com>
Sun, 15 Dec 2013 17:29:21 +0000 (09:29 -0800)
committerGerrit Code Review <gerrit@opendaylight.org>
Mon, 16 Dec 2013 07:57:39 +0000 (07:57 +0000)
commit9b1fd8dda9a1ec24886efcfccd4a64ff8df34ae2
treed27fc76cdf270fd66b7f8987bff82627eb1e36e0
parentcf888ba378fd3332ffe24f898692214af90965d8
Added an UNORDERED option to QueueKeeper

Not all packets require order be preserved, in particular
its actively harmful as a way to deal with PacketIn.

So... I added a QueueType enum {DEFAULT, UNORDERED} (so
we could in principle decide we need different queues in the future)

Kept the existing queueKeeper beahvior for existing invocations
Changed over PacketIn to using UNORDERED

Made PacketInTranslator a bit more robust.

Change-Id: Id835e9840ed26f9ed10e9090ce49ffaa429a002c
Signed-off-by: Ed Warnicke <eaw@cisco.com>
openflowplugin/src/main/java/org/opendaylight/openflowplugin/openflow/md/core/ConnectionConductorImpl.java
openflowplugin/src/main/java/org/opendaylight/openflowplugin/openflow/md/core/translator/PacketInTranslator.java
openflowplugin/src/main/java/org/opendaylight/openflowplugin/openflow/md/queue/QueueKeeper.java
openflowplugin/src/main/java/org/opendaylight/openflowplugin/openflow/md/queue/QueueKeeperLightImpl.java