[ovs-git] [openvswitch/ovs] d317e6: ofproto-dpif-upcall: Translate input port as part ...

GitHub noreply at github.com
Mon Jun 13 20:53:39 UTC 2016


  Branch: refs/heads/branch-2.5
  Home:   https://github.com/openvswitch/ovs
  Commit: d317e66bb8d75af2052143682a08f595dee4a797
      https://github.com/openvswitch/ovs/commit/d317e66bb8d75af2052143682a08f595dee4a797
  Author: Jesse Gross <jesse at kernel.org>
  Date:   2016-06-13 (Mon, 13 Jun 2016)

  Changed paths:
    M ofproto/ofproto-dpif-upcall.c

  Log Message:
  -----------
  ofproto-dpif-upcall: Translate input port as part of upcall translation.

When we generate wildcards for upcalled flows, the flows and therefore
the wildcards, are in OpenFlow format. These are mostly the same but
one exception is the input port. We work around this problem by simply
performing an exact match on the input port when generating netlink
formatted keys. (This does not lose any information in practice because
action translation also always exact matches on input port.)

While this works fine for kernel based flows, it misses the userspace
datapath, which directly consumes the OFP format mask for the input
port. The effect of this is that the in_port mask is sometimes only
the lower 16 bits of the field. (This is because OFP format is a 16-bit
value stored in a 32-bit field. The full width of the field is initialized
with an exact match mask but certain operations result in cleaving this
down to 16 bits.) In practice this does not cause a problem because datapath
port numbers are almost always in the lower 16 bits of the range anyways.

This moves the masking of the datapath format field to translation so that
all datapaths see the same result. This also makes more sense conceptually
as the input port in the flow is also in ODP format at this stage.

Signed-off-by: Jesse Gross <jesse at kernel.org>
Acked-by: Daniele Di Proietto <diproiettod at vmware.com>




More information about the git mailing list