aboutsummaryrefslogtreecommitdiff
path: root/drivers/net
diff options
context:
space:
mode:
authorDavid S. Miller2014-02-28 17:05:32 -0500
committerDavid S. Miller2014-02-28 17:05:32 -0500
commit750f679cfc8323342f1663c69c99be686f79f3ff (patch)
tree1ef358c776a1493ba1d2e6786bf070b05e960c48 /drivers/net
parent4e76ca7f3e4c4b100f19b1bdfc1ed2b541d045e2 (diff)
parent7240cdec60b136f3e64a453c7fbded4ed1aa047e (diff)
Merge branch '6lowpan'
Alexander Aring says: ==================== 6lowpan: reimplementation of fragmentation handling this patch series reimplementation the fragmentation handling of 6lowpan accroding to rfc4944 [1]. The first big note is, that the current fragmentation behaviour isn't rfc complaint. The main issue is a wrong datagram_size value which needs to be: datagram_size = ipv6_payload + ipv6 header + (maybe compressed transport header, currently only udp is supported) but the current datagram_size value is calculated as: datagram_size = ipv6_payload Fragmentation work in a linux<->linux communication only. Why reimplementation? I reimplemted the reassembly side only. The current behaviour is to allocate a skb with the reassembled size and hold all fragments in a list, protected by a spinlock. After we received all fragments (detected by the sum of all fragments, it begins to place all fragments into the allocated skb). This reassembly implementation has some race condition. Additional I make it more rfc complaint. The current implementation match on the tag value inside the frag header only, but rfc4944 says we need to match on dst addr(mac), src addr(mac), tag value, datagram_size value. [2] The new reassembly handling use the inet_frag api (I mean the callback interface of ipv6 and ipv4 reassembly). I looked into ipv6 and wanted to see how ipv6 is dealing with reassembly, so I based my code on this implementation. On the sending side to generate the fragments I improved the current code to use the nearest 8 divided payload. (We can do that, because the mac layer has a dynamic size, so it depends on mac_header how big we can do the payload). Of course I fix also the reassembly/sending side to be rfc complaint now. Regards Alexander Aring [1] http://tools.ietf.org/html/rfc4944 [2] http://tools.ietf.org/html/rfc4944#section-5.3 changes since v2: - rework checkpatch code style issue patch. Merge two pr_debugs into one pr_debug. changes since v3: - rename 6lowpan.ko to 6lowpan_rtnl.c in commit msg of patch 5/8. changes since v4: - Add a new patch 2/8 to introduce lowpan_uncompress_size function. Also improving this function a little bit. - Add a new patch 4/8 to change tag value to __be16. - use skb_header_reset function on FRAG1 only, which should have the lowpan header. See lowpan_get_frag_info function. (slightly improving of fragmentation header parsing). - changes types of variables to u16 in lowpan_skb_fragmentation. - use lowpan_uncompress_size instead of storing necessary information in skb control block, this can be destroyed after dev_queue_xmit call. Thanks David for this hint. - remove Tested-by: Martin Townsend <martin.townsend@xsilon.com>, because too many funcionality change. changes since v5: - handle lowpan_addr_mode_size with lookup table. changes since v6: - remove unnecessary parameter in lowpan_frag_queue. - fix commit message in patch 8/8 which included a describtion of adding the lownpan_uncompress_size function. This was splitted in a seperate patch. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions