On Thu, 27 Nov 2014, Ben Pfaff wrote:


I'd suggest doing a "git bisect" run to find the point at which tests
started failing due to endian problems.


Hi Ben,

test case 'tunnel_push_pop - action', which has been introduced by commit
a36de779d739cdcd72c65c67a547a786798b595a does fail on a bigendian-system

[root@ppc64 ovs-test]# git rev-parse HEAD
1cea007c92e6b33f194fd7acbba9795e03b10a19

commit a36de779d739cdcd72c65c67a547a786798b595a
Author: Pravin B Shelar <pshe...@nicira.com>
Date:   Tue Nov 11 11:53:47 2014 -0800

    openvswitch: Userspace tunneling.

    Following patch adds support for userspace tunneling. Tunneling
needs three more component first is routing table which is configured by caching kernel routes and second is ARP cache which build automatically
    by snooping arp. And third is tunnel protocol table which list all
    listening protocols which is populated by vswitchd as tunnel ports
    are added. GRE and VXLAN protocol support is added in this patch.

    Tunneling works as follows:
    On packet receive vswitchd check if this packet is targeted to tunnel
    port. If it is then vswitchd inserts tunnel pop action which pops
    header and sends packet to tunnel port.
    On packet xmit rather than generating Set tunnel action it generate
    tunnel push action which has tunnel header data. datapath can use
    tunnel-push action data to generate header for each packet and
    forward this packet to output port. Since tunnel-push action
    contains most of packet header vswitchd needs to lookup routing
    table and arp table to build this action.

    Signed-off-by: Pravin B Shelar <pshe...@nicira.com>
    Acked-by: Jarno Rajahalme <jrajaha...@nicira.com>
    Acked-by: Thomas Graf <tg...@noironetworks.com>
    Acked-by: Ben Pfaff <b...@nicira.com>


testsuite.log:
see http://openvswitch.org/pipermail/discuss/2014-November/015678.html

Thanks,
Mijo

_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to