- 22 Aug, 2016 9 commits
-
-
- Revisiting netty configuration based on: -- http://normanmaurer.me/presentations/2014-facebook-eng-netty/slides.html#11.0 -- http://normanmaurer.me/presentations/2014-facebook-eng-netty/slides.html#14.0 Change-Id: I6fe5586908ce2b7c87fd00c8f9da6cca3d907d10
Yuta HIGUCHI authored
- 19 Aug, 2016 19 commits
-
-
The MP2SP intent doesn't support having the egress port in the in ingress port list. Change-Id: I84471b9fce9c1dc072f3dce3d907ba86ba65a575
Jonathan Hart authored -
Its ARP packet processor conflicts with the other ARP proxies for the hard-coded particular IP address 10.0.0.2 Change-Id: Iec4931510f182a28d097b715433781798649b800
Hyunsun Moon authored -
- If the field type is fixed and the type is final, Class info can be omitted - Annotations serializer to use optimization based on the fact Map<String, String> and non-null key/value - Reduce number of Map copy required for ImmutableMap serializer - Reduce number of array copy behind Immutable{List, Set} serializer Change-Id: Ie467a943a33fbfb43b289b8b71ad91ee5890bfb0Yuta HIGUCHI authored -
- WARN:Serialized bytes are not binary compatible - Release summary: https://github.com/EsotericSoftware/kryo/releases/tag/kryo-parent-4.0.0 - KryoNamespace: stop using direct buffer This might fix ONOS-5130 Change-Id: I6e1e00f147a90ae8bfded78b2fa3a77158602c76
Yuta HIGUCHI authored
-
- 18 Aug, 2016 8 commits
-
-
Note that this also fixes the race condition with showing selected intent. Change-Id: Icf3cd168bca985136d3ca6c63d98aa193a476d00
Simon Hunt authored -
SimpleChannelInboundHandler generates `message` instance check code on the fly, using JavaAssist. Which was not working, when a new Connection was created on the thread outside of NettyMessagingManager bundle, which did not have access to netty classes. - Implemented equivalent for SimpleChannelInboundHandler<InternaleMessage> without specifying type parameter, avoiding on the fly code generation. Other changes: - Add a method in IpAddress to return InetAddress instance. Change-Id: Ie97294a5650683457b9395e773269c5232d8e602
Yuta HIGUCHI authored -
The idea is to allow applications to contribute NeighbourMessageHandlers to handle ARP/NDP packets coming from a particular ConnectPoint, Interface or with a particular traffic selector. Applications can contribute different handlers for different ports, because they know how those ports will be used. Also, multiple applications can contribute handlers for different ports/interfaces without having to have one ARP handler for the entire network. The framework provides actions that the handler can choose to take - flood, proxy, reply, drop. The handler is free to implement some other action if none of these fit what it needs to do. The framework also handles many of the common tasks for ARP handlers, like parsing packets, abstracting the differences between ARP and NDP, implementing actions like replying to a request. This allows handlers to be very simple and easy to understand and implement. Change-Id: I313c723e9ebc3d0816eb79870ee0536780e7a640
Jonathan Hart authored
-
- 17 Aug, 2016 4 commits
-
-
- Should fix following warnings: (no name): long already registed as 7. Skipping 326. (no name): class org.onlab.packet.Ip4Address already registed as 70. Skipping 327. Change-Id: I5a3ee1a219b567617f964ddaca16b0cc9dcef5ea
Yuta HIGUCHI authored
