On Sun, Jan 27, 2013 at 04:58:09PM -0800, Ethan Jackson wrote:
> From: Jesse Gross <je...@nicira.com>
> 
> The kernel tunneling code currently needs to handle a large number
> of operations when tunnel packets are encapsulated and
> decapsulated.  Some examples of this are: finding the correct
> tunnel port on receive, TTL and ToS inheritance, ECN handling, etc.
> All of these can be done on a per-flow basis in userspace now that
> we have both the inner and outer header information, which allows
> us to both simplify the kernel and take advantage of userspace's
> information.  Once tunnel packets are redirected into this code,
> the redundant pieces can be removed from other places.
> 
> Signed-off-by: Jesse Gross <je...@nicira.com>
> Signed-off-by: Ethan Jackson <et...@nicira.com>

I looked over this briefly but I think we fully reviewed it earlier.
The only change I noticed was the new void_tnl_port.  I didn't
scrutinize that but it seemed straightforward.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev

Reply via email to