Thanks for pointing this out, Jon. This limitation, however, does not prevent bridging from working in 32-bit architecture. The API/CLI here for adding IP to MAC address mapping is to be used for ARP termination in the bridge domain. So the limitation is that ARP termination is not supported for 32-bit architecture. It is an optional feature that can be enabled for a bridge domain and is disabled by default.
Regards, John From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On Behalf Of Jon Loeliger Sent: Thursday, March 16, 2017 12:40 PM To: Dave Barach (dbarach) <dbar...@cisco.com> Cc: vpp-dev <vpp-dev@lists.fd.io> Subject: Re: [vpp-dev] problems in mips32 From: vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io> [mailto:vpp-dev-boun...@lists.fd.io<mailto:vpp-dev-boun...@lists.fd.io>] On Behalf Of ??? Sent: Wednesday, March 15, 2017 9:52 PM To: vpp-dev <vpp-dev@lists.fd.io<mailto:vpp-dev@lists.fd.io>> Subject: [vpp-dev] problems in mips32 Guys, I'm looking forward to run vpp in mips32 arch,but problem was caused by "clib_calljmp","clib_setjmp" and "clib_longjmp". Thanks, Xinying Xue Also, be aware that there is a hard-coded limit requiring a 64-bit uword in the L2 bridge code as well. Here in src/vnet/l2/l2_bd.c: /** * Add/delete IP address to MAC address mapping. * * The clib hash implementation stores uword entries in the hash table. * The hash table mac_by_ip4 is keyed via IP4 address and store the * 6-byte MAC address directly in the hash table entry uword. * * @warning This only works for 64-bit processor with 8-byte uword; * which means this code *WILL NOT WORK* for a 32-bit prcessor with * 4-byte uword. */ u32 bd_add_del_ip_mac (u32 bd_index, u8 * ip_addr, u8 * mac_addr, u8 is_ip6, u8 is_add) HTH, jdl
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
