From: "Phoebe Buckheister" <phoebe.buckheis...@itwm.fraunhofer.de> Date: Tue, 4 Mar 2014 23:49:33 +0100
> I didn't mean the runtime cost of any conversion that might happen, I was > thinking about how much these conversions would affect the code that uses > these header structs. While for the u16/u32 fields this might be not much, > it will be more for the hardware address fields since these are stored as > the little endian encoding of u64 field you get when reading the u8[8] as > a __be64. If I understand you correctly, these fields would also have to > be in network byte order in the header struct, introducing copy-and-swaps > in every upper layer that uses those addresses and making address matching > harder since memcmp won't work anymore. SUre it would, store the addresses in your internal data structures as a __be64 too. That's what IPV4/IPV6 do, we store addresses and ports in the socket in network byte order. Comparisons just work. ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Linux-zigbee-devel mailing list Linux-zigbee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel
